huntrule

Grafana Web Path Traversal Exploitation (CVE-2021-43798) With 200 Responses

Alerts on Grafana web requests with traversal patterns in the URI query that return HTTP 200.

FreeReviewedSigma · Critical · v5
Category
webserver
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-12-08
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 identifies Grafana web requests where the URL query contains a deep traversal sequence ('/../../../../../../../') and the HTTP response status is 200. It matters because successful path traversal can allow an attacker to reach unintended server paths, often enabling unauthorized access or further exploitation. The detection relies on webserver HTTP telemetry, specifically the request URI query string and the resulting status code.

Reporting behind it

Related detections9 linkedT1190 — drag to rearrange
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
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)
Grafana Web Path Traversal Exploitation (CVE-2021-43798) With 200 Responses
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.