Webserver CVE-2019-11510 Exploitation Attempt via Guacamole URI

Alerts on web requests with a Guacamole-related URI query pattern associated with a Pulse Secure CVE-2019-11510 exploitation attempt.

FreeReviewedSigma · Critical · v5
Category
webserver
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2019-11-18
Updated
2026-07-31

ATT&CK techniques

Initial Access
  1. Recon

  2. Resource Dev

  3. Execution

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule identifies web requests whose URI query contains a pattern targeting the Guacamole path associated with CVE-2019-11510. Attackers may use crafted requests to reach vulnerable Pulse Secure components and attempt initial access. The detection relies on webserver request telemetry, specifically the captured request URI query string.

Related detections9 linkedT1190 — drag to rearrange
Malicious SharePoint ToolShell Exploitation via ToolPane Endpoint
Malicious Exchange Mailbox Export to ASPX via New-MailboxExportRequest
Suspicious Shell Spawned by ActiveMQ Java Process
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
Webserver CVE-2019-11510 Exploitation Attempt via Guacamole URI
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.