Security readout for executives and security teams
Plain-English summary
CVE-2017-18082 is an Atlassian Bamboo cross-site scripting issue in versions before 6.2.3. A branch name could cause arbitrary HTML or JavaScript to run when viewed in the plan branch configuration area. Business risk depends on who can influence branch names and who uses the affected Bamboo screens.
Executive priority
Treat as a targeted remediation item, not a crisis from the available evidence. Prioritize faster if Bamboo is broadly accessible, internet-facing, or used by external contributors.
Technical view
The source describes an XSS vulnerability in Bamboo's plan configure branches resource. The injection vector is the branch name. Affected product evidence is limited to Atlassian Bamboo versions prior to 6.2.3, with no CVSS, CWE, workaround, or exploit details provided in the bundle.
Likely exposure
Organizations running Atlassian Bamboo before 6.2.3 are potentially exposed, especially where Bamboo is reachable by many users or branch names can be influenced by less-trusted contributors.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation evidence. The vulnerability is remote XSS, but the public sources here do not define authentication requirements or exploitation preconditions.
Researcher notes
The evidence set is sparse: no CVSS vector, CWE, exploit status, or detailed advisory text is included. Avoid assuming stored versus reflected behavior beyond the stated branch-name XSS in the plan configure branches resource.
Mitigation direction
- Upgrade Atlassian Bamboo to version 6.2.3 or later.
- Review Atlassian BAM-19666 for vendor-confirmed details and any guidance.
- Restrict Bamboo access to trusted users until the upgrade is complete.
- Limit who can create or influence branch names in connected workflows.
Validation and detection
- Inventory Bamboo deployments and confirm all versions are 6.2.3 or later.
- Check whether any internet-facing Bamboo instance is below 6.2.3.
- Review branch names for unexpected HTML or JavaScript-like content.
- Confirm plan branch configuration pages behave normally after remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2017-18082 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://jira.atlassian.com/browse/BAM-19666CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.