BambooApplication · Atlassian
CVE-2017-14589
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 · uneditedIt was possible for double OGNL evaluation in FreeMarker templates through Struts FreeMarker tags to occur. An attacker who has restricted administration rights to Bamboo or who hosts a website that a Bamboo administrator visits, is able to exploit this vulnerability to execute Java code of their choice on systems that run a vulnerable version of Bamboo. All versions of Bamboo before 6.1.6 (the fixed version for 6.1.x) and from 6.2.0 before 6.2.5 (the fixed version for 6.2.x) 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 confidenceA double OGNL (Object-Graph Navigation Language) evaluation vulnerability exists in Atlassian Bamboo's FreeMarker template processing through Struts FreeMarker tags. This allows remote code execution by injecting malicious OGNL expressions into template parameters, enabling attackers to execute arbitrary Java code on the affected system.
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.1.6>= 6.2.0, < 6.2.5CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Bamboo version numberLog into Bamboo as an administrator and navigate to Administration > About, or check the version from the footer of any Bamboo page. If CLI access is available, check the installation directory for a version file or run: java -jar bamboo-home/WEB-INF/lib/bamboo-core-*.jar --version 2>/dev/null or inspect the application startup logs.Affected if The displayed version is lower than 6.1.6, or falls between 6.2.0 and 6.2.5 (inclusive of 6.2.0 but exclusive of 6.2.5).
-
Identify Bamboo installation pathLocate the Bamboo home directory and web application directory. On Linux systems this is commonly at /opt/atlassian/bamboo or /var/atlassian/application-data/bamboo. On Windows it is typically C:\Program Files\Atlassian\Bamboo or within the home directory.Affected if The installation path exists and contains Bamboo web application files, indicating the vulnerable component is present.
-
Verify Struts FreeMarker tags are in useExamine Bamboo web application files for the presence of Struts FreeMarker tag libraries. Check the WEB-INF/lib directory for struts2-core-*.jar and freemarker-*.jar files. Inspect JSP or FreeMarker templates for tags like <@s.form> or similar Struts tags that trigger OGNL evaluation.Affected if Struts2 core libraries and FreeMarker integration are present in the deployed web application, confirming the attack surface exists.
-
Check if Bamboo web interface is exposedDetermine if the Bamboo server is accessible over HTTP/HTTPS from the network. Review firewall rules, reverse proxy configurations, and Bamboo's base URL settings in the administration console under General Configuration > Base URL.Affected if The Bamboo web interface is accessible to network users, making the OGNL injection vector reachable.
A user is affected if their Bamboo version is either below 6.1.6 or between 6.2.0 and 6.2.4 inclusive, and the web interface is network-accessible with Struts FreeMarker capabilities present.
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.
dbcve · scoped6.1.66.2.5
Upgrade Bamboo to version 6.1.6 or later (for 6.1.x branches) or 6.2.5 or later (for 6.2.x branches). If immediate patching is not possible, restrict administrative access and prevent admins from visiting untrusted websites that could trigger the attack vector.
6.1.6 (for 6.1.x branch) or 6.2.5 (for 6.2.x branch) - or latest supported version
- Back up your Bamboo instance (database and home directory) before upgrading
- Stop the Bamboo service
- If running Bamboo 6.1.x: upgrade to version 6.1.6 or later
- If running Bamboo 6.2.x: upgrade to version 6.2.5 or later
- Review the release notes for the target version for any configuration or migration requirements
- Start the Bamboo service and verify the upgrade was successful
- Confirm the new version by checking Bamboo administration > About
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Bamboo
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14589 — 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-14589 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