huntrule

Atlassian Bitbucket Command Injection Attempt via Archive API Parameters (Webserver)

Alerts on Bitbucket REST archive query parameters containing a %00--exec execution marker.

FreeReviewedSigma · High · v5
Category
webserver
Author
Nasreddine Bencherchali (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2022-09-29
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 HTTP requests to a Bitbucket REST API endpoint that include parameters indicative of a command injection attempt targeting the archive functionality. Attackers may use crafted query strings to trigger unintended command execution on the Bitbucket server. The detection relies on webserver telemetry capturing the requested URI query string and matching specific substrings associated with the exploit attempt.

Reporting behind it

Related detections9 linkedT1190 — drag to rearrange
Possible SharePoint ToolShell ToolPane Exploitation Attempt (via webserver)
Possible Apache ActiveMQ Exploitation via Java Spawning Command Shell (via process_creation)
Malicious Veeam CVE-2023-27532 Exploitation Enabling xp_cmdshell via VeeamHax (via process_creation)
Suspicious PraisonAI Unauthenticated Config Endpoint Access via Webserver
Malicious Langflow Build Public Temp RCE Access via Webserver
Suspicious PraisonAI Vulnerability Scanner User Agent via Webserver
Malicious LiteLLM Authentication SQL Injection via Web Request (via webserver)
Possible Marimo Unauthenticated Terminal WebSocket Access via Web Request (via webserver)
Possible React2Shell Next.js Prototype Pollution Exploitation via Web Request (via webserver)
Atlassian Bitbucket Command Injection Attempt via Archive API Parameters (Webserver)
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.