huntrule

JVM Process Execution Exceptions in Application Logs

Flags JVM error logs showing failed process execution (ProcessBuilder/ProcessImpl) that may reflect attempted command execution.

FreeReviewedSigma · High · v5
Product
jvm
Category
application
Author
Moti Harmats (SigmaHQ), DRL 1.1
Published
2023-02-11
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Initial Access

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule flags application error logs that indicate failed process execution in JVM-based applications, including messages such as 'Cannot run program' and references to Java process APIs (java.lang.ProcessImpl, java.lang.ProcessBuilder). Such failures can occur when an attacker attempts to trigger arbitrary command execution or when exploit attempts fail due to input validation or runtime restrictions. The detection relies on collected application error log text containing specific exception keywords.

Reporting behind it

Related detections9 linkedT1190 — drag to rearrange
Cleo Autorun Exploitation via Healthcheck File Drop
Suspicious SharePoint Worker Process Spawning Command Interpreter via ToolShell
Malicious IIS Worker Process Spawning Command Shell Reconnaissance
Potential StyleSmuggler (CVE-2026-75650) Exploitation Attempt - Magento GraphQL Styles Parameter (via webserver)
Cisco IOS XE Configuration Change by Web UI WSMA User
Possible React2Shell CVE-2025-55182 Prototype Pollution Exploitation
Possible Next.js Middleware Auth Bypass via X-Middleware-Subrequest Header (CVE-2025-29927)
Possible Ivanti Pulse Connect Secure Command Injection via License Keys-Status Endpoint (via webserver)
Possible Ivanti Pulse Connect Secure Auth Bypass via TOTP Backup Code Path Traversal (via webserver)
JVM Process Execution Exceptions in Application Logs
Pivot detection · T1190 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.