| CVE-2017-16857 | Date: (C)2017-12-06 (M)2023-12-22 |
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.
CVSS Score and Metrics +CVSS Score and Metrics -| CVSS V3 Severity: | CVSS V2 Severity: |
| CVSS Score : 8.5 | CVSS Score : 6.0 |
| Exploit Score: 1.8 | Exploit Score: 6.8 |
| Impact Score: 6.0 | Impact Score: 6.4 |
| |
| CVSS V3 Metrics: | CVSS V2 Metrics: |
| Attack Vector: NETWORK | Access Vector: NETWORK |
| Attack Complexity: HIGH | Access Complexity: MEDIUM |
| Privileges Required: LOW | Authentication: SINGLE |
| User Interaction: NONE | Confidentiality: PARTIAL |
| Scope: CHANGED | Integrity: PARTIAL |
| Confidentiality: HIGH | Availability: PARTIAL |
| Integrity: HIGH | |
| Availability: HIGH | |
| | |
