dbcve.org
BambooApplication · Atlassian

CVE-2012-2926

CRITICAL · 9.1 CVSS v3.1 Published 2012-05-22
Fix available
A fix is available. Upgrade to 2.0.9 / 2.1.2 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges Zero-click Patch available

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
Atlassian JIRA before 5.0.1; Confluence before 3.5.16, 4.0 before 4.0.7, and 4.1 before 4.1.10; FishEye and Crucible before 2.5.8, 2.6 before 2.6.8, and 2.7 before 2.7.12; Bamboo before 3.3.4 and 3.4.x before 3.4.5; and Crowd before 2.0.9, 2.1 before 2.1.2, 2.2 before 2.2.9, 2.3 before 2.3.7, and 2.4 before 2.4.1 do not properly restrict the capabilities of third-party XML parsers, which allows remote attackers to read arbitrary files or cause a denial of service (resource consumption) via unspecified vectors.

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

A detailed technical summary for this CVE is being prepared.

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:< 3.3.4>= 3.4, < 3.4.5
ConfluenceApplication
Affected:< 3.5.16
Confluence ServerApplication
Affected:>= 4.0, < 4.0.7>= 4.1, < 4.1.10
CrowdApplication
Affected:< 2.0.9>= 2.1, < 2.1.2>= 2.2.0, < 2.2.9>= 2.3.0, < 2.3.7>= 2.4.0, < 2.4.1
CrucibleApplication
Affected:< 2.5.8>= 2.6, < 2.6.8>= 2.7, < 2.7.12
FisheyeApplication
Affected:< 2.5.8>= 2.6, < 2.6.8>= 2.7, < 2.7.12
JiraApplication
Affected:< 5.0.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

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 · scoped
Upgrade available Upgrade to 2.0.9 / 2.1.2 / 2.2.9 or later
Fixed in 2.0.92.1.22.2.9
Vendor patch confluence.atlassian.com →
Recommended fix High confidence

Upgrade to the minimum fixed version for your product line (Bamboo 3.3.4/3.4.5, Confluence 3.5.16/4.0.7/4.1.10, Crowd 2.0.9/2.1.2/2.2.9/2.3.7/2.4.1, Crucible 2.5.8/2.6.8/2.7.12, Fisheye 2.5.8/2.6.8/2.7.12, or Jira 5.0.1)

  1. 1. Identify the specific Atlassian product (Bamboo, Confluence, Crowd, Crucible, Fisheye, or Jira) running in your environment
  2. 2. Determine the currently installed version using the application's admin interface or system information
  3. 3. For Bamboo: Upgrade to version 3.3.4 (if previously <3.3.4) or 3.4.5 (if >=3.4 and <3.4.5)
  4. 4. For Confluence: Upgrade to version 3.5.16 (if <3.5.16), 4.0.7 (if >=4.0 and <4.0.7), or 4.1.10 (if >=4.1 and <4.1.10)
  5. 5. For Confluence Server: Apply the same version requirements as Confluence
  6. 6. For Crowd: Upgrade to version 2.0.9 (if <2.0.9), 2.1.2 (if >=2.1 and <2.1.2), 2.2.9 (if >=2.2.0 and <2.2.9), or 2.3.7 (if >=2.3.0 and <2.3.7)
  7. 7. For Crucible: Upgrade to version 2.5.8 (if <2.5.8), 2.6.8 (if >=2.6 and <2.6.8), or 2.7.12 (if >=2.7 and <2.7.12)
  8. 8. For Fisheye: Upgrade to version 2.5.8 (if <2.5.8), 2.6.8 (if >=2.6 and <2.6.8), or 2.7.12 (if >=2.7 and <2.7.12)
Caveat Review Atlassian upgrade guides for your specific product version jump as there may be database schema changes and compatibility considerations with plugins

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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