It is possible to bypass the bitbucket auto-unapprove plugin via minimal brute-force because it is relying on asynchronous events on the back-end. This allows an attacker to merge any code into unsuspecting repositories. This affects all versions of the auto-unapprove plugin, however since the auto-unapprove plugin is not bundled with Bitbucket Server it does not affect any particular version of Bitbucket.
References
Link | Resource |
---|---|
https://jira.atlassian.com/browse/BSERV-10439 | Issue Tracking Vendor Advisory |
https://jira.atlassian.com/browse/BSERV-10439 | Issue Tracking Vendor Advisory |
Configurations
Configuration 1 (hide)
|
History
21 Nov 2024, 03:17
Type | Values Removed | Values Added |
---|---|---|
References | () https://jira.atlassian.com/browse/BSERV-10439 - Issue Tracking, Vendor Advisory |
Information
Published : 2017-12-05 16:29
Updated : 2024-11-21 03:17
NVD link : CVE-2017-16857
Mitre link : CVE-2017-16857
CVE.ORG link : CVE-2017-16857
JSON object : View
Products Affected
atlassian
- bitbucket_auto_unapprove_plugin
CWE
CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')