LiveActive security incident?Get immediate response
CVE Record

CVE-2018-5224: Bamboo did not correctly check if a configured Mercurial repository URI contained values that the Windows o...

Bamboo did not correctly check if a configured Mercurial repository URI contained values that the Windows operating system may consider argument parameters. An attacker who has permission to create a repository in Bamboo, edit an existing plan in Bamboo that has a non-linked Mercurial repository, or create a plan in Bamboo either globally or in a project using Bamboo Specs can can execute code of their choice on systems that run a vulnerable version of Bamboo on the Windows operating system. All versions of Bamboo starting with 2.7.0 before 6.3.3 (the fixed version for 6.3.x) and from version 6.4.0 before 6.4.1 (the fixed version for 6.4.x) running on the Windows operating system are affected by this vulnerability.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2018-5224 is an Atlassian Bamboo issue where a Mercurial repository URI could be interpreted by Windows as extra arguments. A permitted Bamboo user could use this to run chosen code on a vulnerable Windows Bamboo server. This matters because Bamboo often has access to build secrets, source code, and deployment paths. Exposure is limited to Atlassian Bamboo instances running on Windows, versions 2.7.0 before 6.3.3 or 6.4.0 before 6.4.1, where users can configure relevant Mercurial repositories or plans. Prioritize remediation for Windows Bamboo servers because successful abuse gives code execution on CI infrastructure. Treat this as high business risk when Bamboo holds credentials, source access, deployment keys, or production release authority. Mitigation focus: Upgrade affected Bamboo 6.3.x deployments to 6.3.3 or later.; Upgrade affected Bamboo 6.4.x deployments to 6.4.1 or later.; Review Atlassian guidance for any version-specific remediation details..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2018-5224 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AtlassianBamboo2.7.1, unspecified, 6.4.0, unspecifiedListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.