dbcve.org
BambooApplication · Atlassian

CVE-2017-18041

MEDIUM · 5.4 CVSS v3.0 Published 2018-02-02
Fix available
A fix is available. Upgrade to 6.2.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
The viewDeploymentVersionJiraIssuesDialog resource in Atlassian Bamboo before version 6.2.0 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in the name of a release.

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 confidence

This is a stored Cross-Site Scripting (XSS) vulnerability in Atlassian Bamboo. Attackers can inject malicious HTML or JavaScript through the 'name' parameter of a release, which then gets rendered in the viewDeploymentVersionJiraIssuesDialog resource without proper sanitization. The vulnerability affects Bamboo versions prior to 6.2.0.

MitigationUpgrade Atlassian Bamboo to version 6.2.0 or later to receive the security patch. As a compensating control, implement strict input validation on release names and ensure output encoding is applied when displaying release information in the UI.

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
Affected:< 6.2.0

CVSS 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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Bamboo installation and version
    Access the Bamboo web interface and check the version displayed in the footer, or check the 'atlassian-bamboo' configuration file or the BAMBOO_HOME/VERSION.txt file for the installed version number
    Affected if The installed version is lower than 6.2.0 (e.g., 6.1.x, 6.0.x, 5.x, etc.)
  2. Locate release management functionality
    Navigate to the deployment section of Bamboo where releases are managed. This is typically found under Builds > Deployments > Releases or similar path depending on the UI version
    Affected if You have deployment releases configured and the Bamboo version is below 6.2.0
  3. Inspect release names for potential XSS payloads
    Examine the names of all releases in the deployment project. Look for any release entries that contain HTML tags (such as <script>, <img>, <iframe>) or JavaScript event handlers (onclick, onerror, etc.) in the name field
    Affected if Any release name contains raw HTML, script tags, or JavaScript code that could execute in a browser
  4. Verify access to the vulnerable endpoint
    Attempt to access the viewDeploymentVersionJiraIssuesDialog resource via direct URL construction or check if the endpoint exists in the Bamboo REST API or UI paths. This is typically related to the dialog that shows Jira issues linked to deployment versions
    Affected if The endpoint is accessible and the Bamboo version is below 6.2.0 with suspicious release names present

You are affected if Atlassian Bamboo is installed with a version lower than 6.2.0 AND there is at least one release name containing unsanitized HTML or JavaScript code that could be rendered in the deployment version Jira issues dialog.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 6.2.0 or later
Fixed in 6.2.0
Interim mitigation

Upgrade Atlassian Bamboo to version 6.2.0 or later to receive the security patch. As a compensating control, implement strict input validation on release names and ensure output encoding is applied when displaying release information in the UI.

Fix this in Bamboo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-18041 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-18041 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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