Atlassian Bitbucket Server and Data Center Command Injection
CVE-2022-36804 is a high-severity improper neutralization of special elements used in an OS command vulnerability in Bitbucket Server from Atlassian, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 7.6.17, 7.17.10, 7.21.4 as the first without the flaw, so updating Bitbucket Server to one of those releases or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on September 30, 2022, which means attacks have been observed in the wild.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Update Bitbucket Server to 7.6.17 or 7.17.10 or 7.21.4 or 8.0.3, whichever matches your release line, or a later version.
- Update Bitbucket Data Center to 7.6.17 or 7.17.10 or 7.21.4 or 8.0.3, whichever matches your release line, or a later version.
- Update Bitbucket to 7.6.17 or 7.17.10 or 7.21.4 or 8.0.3, whichever matches your release line, or a later version.
- CISA's required action: Apply updates per vendor instructions.
- Read the advisory on jira.atlassian.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Atlassian | Bitbucket Server | 7.0.0; before 7.6.17; 7.7.0; before 7.17.10; 7.18.0; before 7.21.4; 8.0.0; before 8.0.3; and 6 more ranges | 7.6.17, 7.17.10, 7.21.4, 8.0.3, 8.1.3, 8.2.2 |
| Atlassian | Bitbucket Data Center | 7.0.0; before 7.6.17; 7.7.0; before 7.17.10; 7.18.0; before 7.21.4; 8.0.0; before 8.0.3; and 6 more ranges | 7.6.17, 7.17.10, 7.21.4, 8.0.3, 8.1.3, 8.2.2 |
| Atlassian | Bitbucket | 7.0.0 up to, but not including, 7.6.17; 7.7.0 up to, but not including, 7.17.10; 7.18.0 up to, but not including, 7.21.4; 8.0.0 up to, but not including, 8.0.3; 8.1.0 up to, but not including, 8.1.3; 8.2.0 up to, but not including, 8.2.2; 8.3.0 | 7.6.17, 7.17.10, 7.21.4, 8.0.3, 8.1.3, 8.2.2 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.8 | High | NVD |
| CVSS 3.1 | 8.8 | High | CISA (ADP) |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Special Elements used in an OS Command
The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command before it is sent to a downstream component.
How developers prevent this class of flaw
- If at all possible, use library calls rather than external processes to recreate the desired functionality.
- For any data that will be used to generate a command to be executed, keep as much of that data out of external control as possible. For example, in web applications, this may require storing the data locally in the session's state instead of sending it out to the client in a hidden form field.
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
More Improper Neutralization of Special Elements used in an OS Command vulnerabilities (CWE-78)
Timeline
- CVE record published.
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- Deadline for US federal agencies to remediate, set by CISA.
- CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
- jira.atlassian.com/browse/BSERV-13438Issue Tracking, Release Notes
Third-party and government advisories
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-36804US Government Resource
Technical write-ups (may include proof of concept)
- packetstormsecurity.com/files/168470/Bitbucket-Git-Command-Injection.htmlExploit, Third Party Advisory, VDB Entry
- packetstormsecurity.com/files/171453/Bitbucket-7.0.0-Remote-Command-Execution.htmlExploit, Third Party Advisory, VDB Entry
Other vulnerabilities in Bitbucket Server
- 7.5 High severity
- 8.8 High severity
- 9.8 Critical severity
- 8.8 High severity
- 9.8 Critical severity
Recent Improper Neutralization of Special Elements used in an OS Command vulnerabilities
- 9.8 Critical severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.