high
8.5
CWE
362
Advisory Published
Updated

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

Affected SoftwareAffected VersionHow to fix
Atlassian Bitbucket Auto Unapprove Plugin=1.0.0
Atlassian Bitbucket Auto Unapprove Plugin=1.0.0-beta1
Atlassian Bitbucket Auto Unapprove Plugin=1.1.0
Atlassian Bitbucket Auto Unapprove Plugin=1.2.0
Atlassian Bitbucket Auto Unapprove Plugin=2.0.1
Atlassian Bitbucket Auto Unapprove Plugin=2.0.2
Atlassian Bitbucket Auto Unapprove Plugin=2.0.4
Atlassian Bitbucket Auto Unapprove Plugin=2.1.1
Atlassian Bitbucket Auto Unapprove Plugin=2.1.3
Atlassian Bitbucket Auto Unapprove Plugin=2.2.0
Atlassian Bitbucket Auto Unapprove Plugin=3.0.0

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

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2017-16857?

    CVE-2017-16857 has a high severity rating as it allows attackers to bypass the auto-unapprove functionality and merge unauthorized code.

  • How do I fix CVE-2017-16857?

    To fix CVE-2017-16857, upgrade the Atlassian Bitbucket Auto Unapprove Plugin to the latest version available from Atlassian.

  • Which versions of the Auto Unapprove Plugin are affected by CVE-2017-16857?

    CVE-2017-16857 affects all versions of the Atlassian Bitbucket Auto Unapprove Plugin.

  • What potential impact does CVE-2017-16857 have on repositories?

    CVE-2017-16857 enables attackers to merge any code into repositories without proper approval, potentially leading to unauthorized changes.

  • Is there a workaround for CVE-2017-16857?

    There is no widely documented workaround for CVE-2017-16857; the best method is to upgrade to a patched version.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203