cve.bz

CVE-2017-8907 atlassian bamboo: Incorrect Authorization

8.8 highEPSS 1.7%

High (8.8) in atlassian bamboo. EPSS 1.7% estimated probability of exploitation activity in the next 30 days.

On this page
Atlassian Bamboo 5.x before 5.15.7 and 6.x before 6.0.1 did not correctly check if a user creating a deployment project had the edit permission and therefore the rights to do so. An attacker who can login to Bamboo as a user without the edit permission for deployment projects is able to use this vulnerability, provided there is an existing plan with a green build, to create a deployment project and execute arbitrary code on an available Bamboo Agent. By default a local agent is enabled; this means that code execution can occur on the system hosting Bamboo as the user running Bamboo.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
1.7% (unchanged from 1.7% a week ago; 1.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 77th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2024-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2017-8907 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-8907?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-8907?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-8907 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
atlassian:bamboo5.0
atlassian:bamboo5.0:beta1
atlassian:bamboo5.0:beta2
atlassian:bamboo5.0:beta3
atlassian:bamboo5.0:rc1
atlassian:bamboo5.0.1
atlassian:bamboo5.1
atlassian:bamboo5.1.1
atlassian:bamboo5.2
atlassian:bamboo5.2.1
atlassian:bamboo5.2.2
atlassian:bamboo5.3
atlassian:bamboo5.4
atlassian:bamboo5.4.1
atlassian:bamboo5.4.2
atlassian:bamboo5.5
atlassian:bamboo5.6
atlassian:bamboo5.6.1
atlassian:bamboo5.6.2
atlassian:bamboo5.7
atlassian:bamboo5.7.1
atlassian:bamboo5.7.2
atlassian:bamboo5.8
atlassian:bamboo5.8.1
atlassian:bamboo5.8.2
atlassian:bamboo5.8.5
atlassian:bamboo5.9
atlassian:bamboo5.9.1
atlassian:bamboo5.9.2
atlassian:bamboo5.9.3
atlassian:bamboo5.9.4
atlassian:bamboo5.9.7
atlassian:bamboo5.11.3
atlassian:bamboo5.12.0
atlassian:bamboo5.12.1
atlassian:bamboo5.12.2
atlassian:bamboo5.12.4
atlassian:bamboo5.12.5
atlassian:bamboo5.13.0
atlassian:bamboo5.13.1
atlassian:bamboo5.13.2
atlassian:bamboo5.14.0
atlassian:bamboo5.14.1
atlassian:bamboo5.14.2
atlassian:bamboo5.14.3
atlassian:bamboo5.14.4.1
atlassian:bamboo5.14.5
atlassian:bamboo5.15.0
atlassian:bamboo5.15.2
atlassian:bamboo5.15.3
atlassian:bamboo5.15.4
atlassian:bamboo5.15.5
atlassian:bamboo6.0.0

References

Check your stackJSON