CVE Vulnerabilities


Improper Neutralization of Special Elements used in a Command ('Command Injection')

Published: Jan 15, 2020 | Modified: Aug 24, 2020
CVSS 3.x
CVSS 2.x

Bitbucket Server and Bitbucket Data Center versions starting from version 3.0.0 before version 5.16.11, from version 6.0.0 before 6.0.11, from version 6.1.0 before 6.1.9, from version 6.2.0 before 6.2.7, from version 6.3.0 before 6.3.6, from version 6.4.0 before 6.4.4, from version 6.5.0 before 6.5.3, from version 6.6.0 before 6.6.3, from version 6.7.0 before 6.7.3, from version 6.8.0 before 6.8.2, and from version 6.9.0 before 6.9.1 had a Remote Code Execution vulnerability via certain user input fields. A remote attacker with user level permissions can exploit this vulnerability to run arbitrary commands on the victims systems. Using a specially crafted payload as user input, the attacker can execute arbitrary commands on the victims Bitbucket Server or Bitbucket Data Center instance.


The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.

Affected Software

Name Vendor Start Version End Version
Bitbucket Atlassian 3.0.0 (including) 5.6.11 (excluding)
Bitbucket Atlassian 6.0.0 (including) 6.0.11 (excluding)
Bitbucket Atlassian 6.1.0 (including) 6.1.9 (excluding)
Bitbucket Atlassian 6.2.0 (including) 6.2.7 (excluding)
Bitbucket Atlassian 6.3.0 (including) 6.3.6 (excluding)
Bitbucket Atlassian 6.4.0 (including) 6.4.4 (excluding)
Bitbucket Atlassian 6.5.0 (including) 6.5.3 (excluding)
Bitbucket Atlassian 6.6.0 (including) 6.6.3 (excluding)
Bitbucket Atlassian 6.7.0 (including) 6.7.3 (excluding)
Bitbucket Atlassian 6.8.0 (including) 6.8.2 (excluding)
Bitbucket Atlassian 6.9.0 (including) 6.9.1 (excluding)

Extended Description

Command injection vulnerabilities typically occur when:

Many protocols and products have their own custom command language. While OS or shell command strings are frequently discovered and targeted, developers may not realize that these other command languages might also be vulnerable to attacks. Command injection is a common problem with wrapper programs.

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.