Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

CVE-2017-16857

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.

Published

2017-12-05T16:29:00.453

Last Modified

2025-04-20T01:37:25.860

Status

Deferred

Source

[email protected]

Severity

CVSSv3.0: 8.5 (HIGH)

CVSSv2 Vector

AV:N/AC:M/Au:S/C:P/I:P/A:P

  • Access Vector: NETWORK
  • Access Complexity: MEDIUM
  • Authentication: SINGLE
  • Confidentiality Impact: PARTIAL
  • Integrity Impact: PARTIAL
  • Availability Impact: PARTIAL
Exploitability Score

6.8

Impact Score

6.4

Weaknesses
  • Type: Primary
    CWE-362
Affected Vendors & Products
Type Vendor Product Version/Range Vulnerable?
Application atlassian bitbucket_auto_unapprove_plugin 1.0.0 Yes
Application atlassian bitbucket_auto_unapprove_plugin 1.0.0 Yes
Application atlassian bitbucket_auto_unapprove_plugin 1.1.0 Yes
Application atlassian bitbucket_auto_unapprove_plugin 1.2.0 Yes
Application atlassian bitbucket_auto_unapprove_plugin 2.0.1 Yes
Application atlassian bitbucket_auto_unapprove_plugin 2.0.2 Yes
Application atlassian bitbucket_auto_unapprove_plugin 2.0.4 Yes
Application atlassian bitbucket_auto_unapprove_plugin 2.1.1 Yes
Application atlassian bitbucket_auto_unapprove_plugin 2.1.3 Yes
Application atlassian bitbucket_auto_unapprove_plugin 2.2.0 Yes
Application atlassian bitbucket_auto_unapprove_plugin 3.0.0 Yes
References