Bitbucket Auto Unapprove Plugin
Approved changes feed: RSS · Atom
cpe:2.3:a:atlassian:bitbucket_auto_unapprove_plugin:2.0.1:*:*:*:*:*:*:*
part: a version: 2.0.1 update: *
| Vendor | Atlassian (8acde0d4-2b83-5bd8-8d3f-60d59e0b022e) |
|---|---|
| Product | Bitbucket Auto Unapprove Plugin (75936b22-8d2d-5f16-9b23-30a8d8e5c669) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2017-16857 |
vulnerable | 2026-06-03 14:36:48.709593 |
Details available
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:00:00.000Z
Updated: 2024-09-17T02:01:17.347Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.