VIR Vulnerability Intelligence Relay

CVE-2017-16857

high
Published 2017-12-05 · Modified 2026-05-13
💬 Discuss on Community ✚ Propose mitigation
CVSS v3
8.5
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
CVSS v4 NEW
—
not yet in upstream
VIR risk
8.5

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.

Predictions

Exploit likelihood
90%
Patch ETA
—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

Application impact
VendorProductVersionsFixed
atlassianbitbucket_auto_unapprove_plugin1.0.0
atlassianbitbucket_auto_unapprove_plugin1.1.0
atlassianbitbucket_auto_unapprove_plugin1.2.0
atlassianbitbucket_auto_unapprove_plugin2.0.1
atlassianbitbucket_auto_unapprove_plugin2.0.2
atlassianbitbucket_auto_unapprove_plugin2.0.4
atlassianbitbucket_auto_unapprove_plugin2.1.1
atlassianbitbucket_auto_unapprove_plugin2.1.3
atlassianbitbucket_auto_unapprove_plugin2.2.0
atlassianbitbucket_auto_unapprove_plugin3.0.0

References

CWEs

CWE-362

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.