dbcve.org
BambooApplication · Atlassian

CVE-2018-5224

HIGH · 8.8 CVSS v3.0 Published 2018-03-29
Fix available
A fix is available. Upgrade to 6.3.3 / 6.4.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
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.

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

Bamboo fails to properly sanitize Mercurial repository URI values on Windows, allowing the OS to interpret certain URI components as command arguments. An authenticated attacker with repository create/edit permissions can inject arbitrary code through specially crafted Mercurial repository URIs.

MitigationUpgrade Bamboo to version 6.3.3 or 6.4.1 or later. If upgrading is not immediately possible, restrict user permissions for repository configuration and consider migrating Bamboo off Windows infrastructure.

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:>= 2.7.0, < 6.3.3>= 6.4.0, < 6.4.1

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/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 checks

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

  1. Determine Bamboo version
    Log into the Bamboo administration console and navigate to About (or run: java -jar bamboo-home/WEB-INF/lib/bamboo-[version].jar --version if available). Alternatively, check the WAR file version or the pom.xml in the installation directory.
    Affected if The installed version is >= 2.7.0 and < 6.3.3, OR >= 6.4.0 and < 6.4.1
  2. Confirm the operating system
    Check the OS where Bamboo is running. On the Bamboo server, run 'systeminfo' on Windows or 'uname -a' on Linux/Unix. Also check the Bamboo system info page at /admin/systeminfo.action.
    Affected if The server is running Windows (this vulnerability only affects Windows environments)
  3. Verify Mercurial repository usage
    In Bamboo, go to Repository settings or check the linked repositories under each plan configuration. Look for any repositories configured with Mercurial (HG) as the source type.
    Affected if Mercurial repositories are configured and actively used in Bamboo plans
  4. Review repository permission settings
    Navigate to Bamboo administration > Security > Permissions. Check which users or groups have 'Create Repository' or 'Edit Repository' permissions. Alternatively, review the 'Repository' permissions in project or plan-level security settings.
    Affected if Users other than administrators have repository create or edit permissions enabled

A user is affected if Bamboo is running on Windows, the version falls within the vulnerable ranges (2.7.0 to 6.3.2 or 6.4.0), and Mercurial repositories are configured with users having repository edit permissions.

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.3.3 / 6.4.1 or later
Fixed in 6.3.36.4.1
Interim mitigation

Upgrade Bamboo to version 6.3.3 or 6.4.1 or later. If upgrading is not immediately possible, restrict user permissions for repository configuration and consider migrating Bamboo off Windows infrastructure.

Fix this in Bamboo Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,312.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-5224 — 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-2018-5224 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