CVE-2022-36804
RCE in Atlassian Bitbucket 7.0.0 – 7.6.17
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2022-36804 is a high-severity OS Command Injection (CWE-78) vulnerability in Atlassian Bitbucket. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 0.1% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2022-36804 is a command injection vulnerability affecting multiple API endpoints in Atlassian Bitbucket Server and Data Center. Impacted versions include 7.0.0 prior to 7.6.17, 7.7.0 prior to 7.17.10, 7.18.0 prior to 7.21.4, 8.0.0 prior to 8.0.3, 8.1.0 prior to 8.1.3, 8.2.0 prior to 8.2.2, and 8.3.0 prior to 8.3.1. The flaw, assigned CWE-78 and CWE-88, permits arbitrary code execution when an attacker supplies crafted input to the affected endpoints.
An attacker who already possesses read access to any public or private repository can exploit the issue by sending a single malicious HTTP request. Successful exploitation grants the ability to run arbitrary commands on the Bitbucket server with the privileges of the application process, resulting in full confidentiality, integrity, and availability impact as reflected in the CVSS 8.8 score.
Publicly available references include the Atlassian Jira issue BSERV-13438, which documents the affected releases and the corrected versions, as well as multiple exploit artifacts published on PacketStorm. Upgrading to one of the fixed releases listed in the advisory is the primary mitigation.
PacketStorm hosts working exploit code for the vulnerability, and the EPSS score has reached a peak of 0.9756 with a current value of 0.9440, indicating sustained exploitation interest after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-39504
Vulnerability Data
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…
more
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.
- CWE(s)
- KEV Date Added
- 30 September 2022
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.5V1.2.8V15.2.5
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
PR.PS-06's SDLC practices directly require secure coding and input handling that blocks command-injection defects, yet the single broad outcome leaves many specific neutralization vectors and verification gaps unaddressed.
Routine patching/maintenance can remediate known command-injection CVEs in dependencies (partial forward) but does nothing to stop developers from introducing improper neutralization in custom code (none reverse).
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing and code review target insecure use of operating-system command interfaces, catching command-injection flaws introduced during development.
Secure development lifecycle mandates input validation and command construction practices that directly prevent argument injection.
Application security requirements include explicit rules for safe command-line argument handling and escaping.
Secure architecture principles discourage unsafe command invocation patterns and favor safer APIs.
Secure coding standards explicitly require proper neutralization of command arguments, directly eliminating CWE-88.
Change management can catch unsafe command patterns during reviews but is not a direct mitigation.