Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2022-43781 is a critical-severity Command Injection (CWE-77) vulnerability in Atlassian Bitbucket. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 0.1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.
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-43781 is a command injection vulnerability that arises from unsafe handling of environment variables in Atlassian Bitbucket Server and Data Center. The flaw is tracked under CWE-77 and carries a CVSS 3.1 score of 9.8. An attacker who can control a username value is able to inject operating-system commands that execute with the privileges of the Bitbucket process.
Exploitation requires the ability to set or modify a username; when the instance permits public signup the attack can be performed unauthenticated over the network. Successful exploitation results in arbitrary code execution on the underlying server, giving an attacker full control over the confidentiality, integrity, and availability of the Bitbucket instance and any connected repositories.
Public advisories and patch information are published by Atlassian at the referenced Confluence and Jira locations (https://confluence.atlassian.com/x/Y4hXRg and https://jira.atlassian.com/browse/BSERV-13522).
The CVE maintains a high EPSS score, with a current value of 0.8748 and a recorded peak of 0.9208, indicating sustained exploitation interest after disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-46751
Vulnerability Data
There is a command injection vulnerability using environment variables in Bitbucket Server and Data Center. An attacker with permission to control their username can exploit this issue to execute arbitrary code on the system. This vulnerability can be unauthenticated if…
more
the Bitbucket Server and Data Center instance has enabled “Allow public signup”.
- CWE(s)
Related Threats
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires validation and sanitization of untrusted username input that is passed into environment variables, blocking the command-injection vector.
Limits the privileges of the Bitbucket process so that even successful command injection yields only restricted code execution.
Mandates timely application of the vendor patch that eliminates the unsafe environment-variable handling described in the CVE.
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.
Secure SDLC practices directly require input validation and neutralization that prevent command injection.
Runtime monitoring of software and data can detect anomalous command execution resulting from injection.
Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.
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.
Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.
Security testing in development catches command-injection vulnerabilities before release.
Secure development life cycle mandates input validation and command construction practices that directly prevent command injection.
Application security requirements explicitly call for controls against injection flaws including command injection.
Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.
Environment separation limits the blast radius of an exploited command injection but does not prevent the flaw itself.