BambooApplication · Atlassian
CVE-2017-18081
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 · uneditedThe signupUser resource in Atlassian Bamboo before version 6.3.1 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability through the value of the csrf token cookie.
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 confidenceThe signupUser resource in Atlassian Bamboo before version 6.3.1 contains a cross-site scripting (XSS) vulnerability where the value of the CSRF token cookie is reflected without proper sanitization, allowing remote attackers to inject arbitrary HTML or JavaScript through a malicious cookie value.
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
< 6.3.1CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 Atlassian Bamboo versionCheck the version of Atlassian Bamboo by reviewing the application banner, about page, or checking the 'atlassian-bamboo' version file in the installation directory (commonly in /opt/bamboo/atlassian-bamboo/WEB-INF/lib or via the admin console at /admin/viewAdministrators.action).Affected if The installed version is lower than 6.3.1 (for example, 6.3.0, 6.2.x, 6.1.x, etc.)
-
Confirm signupUser resource is accessibleAccess the Bamboo signup page (typically at /signupUser.action or /user/signup) to verify the self-registration endpoint is available.Affected if The signupUser endpoint responds and the self-signup feature is enabled in Bamboo configuration
-
Verify CSRF token cookie is setLog into Bamboo and examine the HTTP response headers or use browser developer tools to inspect cookies being set. Look for a cookie containing 'csrf' or 'token' in its name.Affected if A CSRF token cookie is being set without the HttpOnly flag or without proper output encoding applied to its value
-
Check cookie configuration in BambooReview the Bamboo configuration files (bamboo-init.properties, bamboo.cfg.xml) or the web.xml to examine how cookies, particularly security-related cookies, are configured and whether input validation is applied.Affected if Cookie values from the signup flow are reflected in responses without sanitization or encoding
You are affected if your Atlassian Bamboo version is below 6.3.1 AND the signupUser endpoint is accessible with a CSRF token cookie being set and reflected without proper encoding.
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 data6.3.1
Upgrade Atlassian Bamboo to version 6.3.1 or later. Additionally, implement proper output encoding for cookie values and ensure cookies are set with HttpOnly and Secure flags where appropriate.
Fix this in Bamboo
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18081 — 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-18081 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