Possible Ivanti Pulse Connect Secure Command Injection via License Keys-Status Endpoint (via webserver)

PremiumReviewedSigma · Medium · v1
Category
webserver
Author
HuntRule
Published
2026-09-08
Updated
2026-09-08

ATT&CK techniques

Initial Access → Execution
  1. Recon

  2. Resource Dev

  3. Persistence

  4. Priv Esc

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects requests to the Pulse Connect Secure license keys-status API node parameter carrying shell metacharacters. This maps to the command injection flaw where the node name is passed unsanitized into a shell context. An attacker uses this to execute arbitrary operating system commands on the appliance.

Related detections9 linkedT1059 — drag to rearrange
Malicious Command Shell Spawned by SQL Server via Process Creation (via process_creation)
Suspicious Reconnaissance and Payload Download by Node Web Process
Malicious Text4Shell Apache Commons Text Interpolation Payload in HTTP Request
Possible Apache ActiveMQ RCE via Jolokia addNetworkConnector (via webserver)
Possible LiteLLM Unauthenticated Command Execution via MCP Test Endpoints (via webserver)
Possible Ivanti Cloud Services Appliance Command Injection via datetime.php (via webserver)
Possible Log4Shell Exploitation via Java Spawning Shell or Download Utility
Possible Craft CMS RCE via Query-String CLI Option Injection
Possible Aspera Faspex Pre-Auth RCE via YAML Deserialization in package_relay (via webserver)
Possible Ivanti Pulse Connect Secure Command Injection via License Keys-Status Endpoint (via webserver)
Pivot detection · T1059 · 9 related

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