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.
Analysis and contextual insights are available on OpenCVE Cloud.
Remediation
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2017-8031 | 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 | Providers |
|---|---|
| https://jira.atlassian.com/browse/BSERV-10439 |
|
History
No history.
Status: PUBLISHED
Assigner: atlassian
Published:
Updated: 2024-09-17T02:01:17.347Z
Reserved: 2017-11-16T00:00:00.000Z
Link: CVE-2017-16857
No data.
Status : Modified
Published: 2017-12-05T16:29:00.453
Modified: 2026-05-13T00:24:29.033
Link: CVE-2017-16857
No data.
OpenCVE Enrichment
No data.
Weaknesses
EUVD