The commit diff rest endpoint in Bitbucket Server and Data Center before 5.16.10 (the fixed version for 5.16.x ), from 6.0.0 before 6.0.10 (
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.16.10, 6.0.10, 6.1.8, 6.2.6, 6.3.5, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The commit diff rest endpoint in Bitbucket Server and Data Center before 5.16.10 (the fixed version for 5.16.x ), from 6.0.0 before 6.0.10 (the fixed version for 6.0.x), from 6.1.0 before 6.1.8 (the fixed version for 6.1.x), from 6.2.0 before 6.2.6 (the fixed version for 6.2.x), from 6.3.0 before 6.3.5 (the fixed version for 6.3.x), from 6.4.0 before 6.4.3 (the fixed version for 6.4.x), and from 6.5.0 before 6.5.2 (the fixed version for 6.5.x) allows remote attackers who have permission to access a repository, if public access is enabled for a project or repository then attackers are able to exploit this issue anonymously, to read the contents of arbitrary files on the system and execute commands via injecting additional arguments into git commands.
Timeline
- CVE published
- Record last updated
Affected versions
- Atlassian Bitbucket Server
fixed in 5.16.10; From 6.0.0; fixed in 6.0.10; From 6.1.0; fixed in 6.1.8; From 6.2.0; fixed in 6.2.6; From 6.3.0; fixed in 6.3.5; From 6.4.0; fixed in 6.4.3; From 6.5.0; fixed in 6.5.2
- Atlassian Bitbucket Data Center
fixed in 5.16.10; From 6.0.0; fixed in 6.0.10; From 6.1.0; fixed in 6.1.8; From 6.2.0; fixed in 6.2.6; From 6.3.0; fixed in 6.3.5; From 6.4.0; fixed in 6.4.3; From 6.5.0; fixed in 6.5.2