CVE-2017-16857: Race Condition

First published: Tue Dec 05 2017(Updated: )

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.

Credit: security@atlassian.com

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

• collector/nvd-index
• agent/weakness
• agent/references
• agent/severity
• agent/author
• agent/tags
• agent/type
• agent/event
• agent/description
• agent/last-modified-date
• agent/first-publish-date
• agent/softwarecombine
• collector/mitre-cve
• source/MITRE
• vendor/atlassian
• canonical/atlassian bitbucket auto unapprove plugin
• version/atlassian bitbucket auto unapprove plugin/1.0.0
• version/atlassian bitbucket auto unapprove plugin/1.0.0-beta1
• version/atlassian bitbucket auto unapprove plugin/1.1.0
• version/atlassian bitbucket auto unapprove plugin/1.2.0
• version/atlassian bitbucket auto unapprove plugin/2.0.1
• version/atlassian bitbucket auto unapprove plugin/2.0.2
• version/atlassian bitbucket auto unapprove plugin/2.0.4
• version/atlassian bitbucket auto unapprove plugin/2.1.1
• version/atlassian bitbucket auto unapprove plugin/2.1.3
• version/atlassian bitbucket auto unapprove plugin/2.2.0
• version/atlassian bitbucket auto unapprove plugin/3.0.0