BambooApplication · Atlassian
CVE-2017-8907
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAtlassian 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is an authorization bypass vulnerability in Atlassian Bamboo where the application fails to properly check if a user has edit permissions before allowing creation of deployment projects. An authenticated user without deployment project edit rights can create a deployment project and execute arbitrary code on any available Bamboo Agent, including the local agent running on the Bamboo server itself.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
BambooApplication
= 5.0= 5.0.1= 5.1= 5.1.1= 5.2= 5.2.1= 5.2.2= 5.3= 5.4= 5.4.1= 5.4.2= 5.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Bamboo versionAccess the Bamboo administration console and navigate to the 'About' or 'System Information' page to view the installed version numberAffected if The version listed matches any of: 5.0, 5.0.1, 5.1, 5.1.1, 5.2, 5.2.1, 5.2.2, 5.3, 5.4, 5.4.1, 5.4.2, or 5.5
-
Verify deployment projects are enabledIn the Bamboo UI, navigate to 'Deployment' in the project navigation and confirm the deployment projects feature is accessible and not disabled at the system levelAffected if Deployment projects feature is active and users can access the deployment project creation interface
-
Confirm user lacks deployment edit permissionReview the permissions for the test user account by going to Administration > Security > Global Permissions or Project permissions, and verify the user does NOT have 'Create Deployment Projects' or equivalent edit rights assignedAffected if The authenticated user account being tested has valid login credentials but does NOT have explicit deployment project edit or create permissions granted in Bamboo's permission scheme
-
Check for unauthorized deployment projectsReview the list of all deployment projects in Bamboo by navigating to the Deployments section and inspecting the audit log or project ownership for any projects created by users who should not have had create permissionsAffected if Deployment projects exist that were created by users without documented deployment edit permissions
You are affected if your Bamboo version is 5.0 through 5.5 and deployment projects are enabled, allowing any authenticated user to potentially create deployment projects and execute code on agents regardless of permission settings.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to Bamboo version 5.15.7 / 6.0.1 or later which includes the proper permission validation for deployment project creation.
Fix this in Bamboo
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8907 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-8907 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data