dbcve.org
CrucibleApplication · Atlassian

CVE-2021-43956

MEDIUM · 6.1 CVSS v3.1 Published 2022-03-16
Fix available
A fix is available. Upgrade to 4.8.9 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
The jQuery deserialize library in Fisheye and Crucible before version 4.8.9 allowed remote attackers to to inject arbitrary HTML and/or JavaScript via a prototype pollution 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 · moderate confidence

The jQuery deserialize library used in Atlassian Fisheye and Crucible contains a prototype pollution vulnerability that allows remote attackers to inject arbitrary HTML and JavaScript via manipulating object prototypes during deserialization. This client-side code injection can lead to Cross-Site Scripting (XSS) attacks.

MitigationUpgrade Fisheye and Crucible to version 4.8.9 or later, which includes the patched jQuery deserialize library that prevents prototype pollution.

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
CrucibleApplication
Affected:< 4.8.9
FisheyeApplication
Affected:< 4.8.9

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Identify installed Fisheye or Crucible version
    Access the product's admin interface or check the application startup logs. Most Fisheye/Crucible installations display the version on the 'About' page in the admin console (typically at /admin/about.vm) or in the header/footer of the UI.
    Affected if The displayed version number is lower than 4.8.9 (e.g., 4.8.8, 4.8.7, 4.7.x, etc.)
  2. Check Fisheye/Crucible version via command line
    If you have shell access to the server, check the version from the installation directory. Look for a version file or use any available CLI tools shipped with the product.
    Affected if The command output or version file shows a version below 4.8.9
  3. Locate the jQuery deserialize library (if accessible)
    Search the application files for 'jquery.deserialize' or 'jquery.deserialize.min.js' - this library is typically bundled in the web application's static resources.
    Affected if The library exists and originates from a version prior to the patched release (the vulnerability exists in the deserialize function allowing prototype manipulation during JSON deserialization)

You are affected if your installed Fisheye or Crucible version is any release prior to 4.8.9, as these versions include the vulnerable jQuery deserialize library that permits prototype pollution leading to XSS.

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.

dbcve · scoped
Upgrade available Upgrade to 4.8.9 or later
Fixed in 4.8.9
Interim mitigation

Upgrade Fisheye and Crucible to version 4.8.9 or later, which includes the patched jQuery deserialize library that prevents prototype pollution.

Recommended fix High confidence

Fisheye/Crucible 4.8.9 or later

  1. 1. Back up your current Fisheye/Crucible installation and database before upgrading.
  2. 2. Download Fisheye/Crucible version 4.8.9 or later from the Atlassian official download center.
  3. 3. Review the Atlassian upgrade guide for your specific installation type (standalone or bundled with Jira).
  4. 4. Stop the Fisheye/Crucible service.
  5. 5. Install the new version by following the standard Atlassian upgrade procedure.
  6. 6. Start the Fisheye/Crucible service.
  7. 7. Verify the upgrade was successful by logging into the admin interface and confirming the version number.
Caveat Review Atlassian upgrade notes for any migration requirements or compatibility considerations with your Jira version

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

Fix this in Crucible Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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