CVE-2017-16857

Description

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.

Category

8.5
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.29%
Vendor Advisory atlassian.com
Affected: Atlassian Auto-Unapprove Plugin (for Bitbucket Server)
Published at:
Updated at:

References

Link Tags
https://jira.atlassian.com/browse/BSERV-10439 vendor advisory issue tracking

Frequently Asked Questions

What is the severity of CVE-2017-16857?
CVE-2017-16857 has been scored as a high severity vulnerability.
How to fix CVE-2017-16857?
To fix CVE-2017-16857, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-16857 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2017-16857 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2017-16857?
CVE-2017-16857 affects Atlassian Auto-Unapprove Plugin (for Bitbucket Server).
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.