cve.bz

CVE-2022-36804 Atlassian Bitbucket Server and Data Center Command Injection Vulnerability

8.8 highKEVExploitEPSS 99%Fix available

High (8.8) in Atlassian Bitbucket Server and Data Center. In CISA KEV since 2022-09-30. EPSS 99% estimated probability of exploitation activity in the next 30 days.

On this page
Multiple API endpoints in Atlassian Bitbucket Server and Data Center 7.0.0 before version 7.6.17, from version 7.7.0 before version 7.17.10, from version 7.18.0 before version 7.21.4, from version 8.0.0 before version 8.0.3, from version 8.1.0 before version 8.1.3, and from version 8.2.0 before version 8.2.2, and from version 8.3.0 before 8.3.1 allows remote attackers with read permissions to a public or private Bitbucket repository to execute arbitrary code by sending a malicious HTTP request. This vulnerability was reported via our Bug Bounty Program by TheGrandPew.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
99% (unchanged from 99% a week ago; 99.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2022-09-30, due 2022-10-21
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2025-01-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-78 Improper Neutralization of Special Elements used in an OS Command (OS Command Injection)
CWE-88 Improper Neutralization of Argument Delimiters in a Command (Argument Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-36804 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-36804?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-36804?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-36804 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Atlassian Bitbucket Serverfrom 7.0.0 before unspecified
Atlassian Bitbucket Serverbefore 7.6.17
Atlassian Bitbucket Serverfrom 7.7.0 before unspecified
Atlassian Bitbucket Serverbefore 7.17.10
Atlassian Bitbucket Serverfrom 7.18.0 before unspecified
Atlassian Bitbucket Serverbefore 7.21.4
Atlassian Bitbucket Serverfrom 8.0.0 before unspecified
Atlassian Bitbucket Serverbefore 8.0.3
Atlassian Bitbucket Serverfrom 8.1.0 before unspecified
Atlassian Bitbucket Serverbefore 8.1.3
Atlassian Bitbucket Serverfrom 8.2.0 before unspecified
Atlassian Bitbucket Serverbefore 8.2.2
Atlassian Bitbucket Serverfrom 8.3.0 before unspecified
Atlassian Bitbucket Serverbefore 8.3.1
Atlassian Bitbucket Data Centerfrom 7.0.0 before unspecified
Atlassian Bitbucket Data Centerbefore 7.6.17
Atlassian Bitbucket Data Centerfrom 7.7.0 before unspecified
Atlassian Bitbucket Data Centerbefore 7.17.10
Atlassian Bitbucket Data Centerfrom 7.18.0 before unspecified
Atlassian Bitbucket Data Centerbefore 7.21.4
Atlassian Bitbucket Data Centerfrom 8.0.0 before unspecified
Atlassian Bitbucket Data Centerbefore 8.0.3
Atlassian Bitbucket Data Centerfrom 8.1.0 before unspecified
Atlassian Bitbucket Data Centerbefore 8.1.3
Atlassian Bitbucket Data Centerfrom 8.2.0 before unspecified
Atlassian Bitbucket Data Centerbefore 8.2.2
Atlassian Bitbucket Data Centerfrom 8.3.0 before unspecified
Atlassian Bitbucket Data Centerbefore 8.3.1

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • Junohea/cve-2022-36804 Harbor Check: matches CVE 0 stars, Python, created
    CVE-2022-36804 Bitbucket command execution and file transfer tool
  • DanielHallbro/CVE-2022-36804-Bitbucket-RCE-Analysis Harbor Check: matches CVE 0 stars, Shell, created
    Full-chain reproduction of CVE-2022-36804 (Bitbucket RCE). Includes a Dockerized laboratory, pspy64 monitoring for null-byte injection veri…

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-6 Argument Injection Likelihood: High · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-88 OS Command Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High
  • CAPEC-41 Using Meta-characters in E-mail Headers to Inject Malicious Payloads Likelihood: High · Severity: High
  • CAPEC-137 Parameter Injection Likelihood: Medium · Severity: Medium
  • CAPEC-174 Flash Parameter Injection Likelihood: High · Severity: Medium
  • CAPEC-460 HTTP Parameter Pollution (HPP) Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON