CrucibleApplication · Atlassian
CVE-2020-4013
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 · uneditedThe review resource in Atlassian Fisheye and Crucible before version 4.8.1 allows remote attackers to inject arbitrary HTML or Javascript via a cross site scripting (XSS) vulnerability through the review objectives.
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 stored cross-site scripting (XSS) vulnerability exists in the review objectives feature of Atlassian Fisheye and Crucible prior to version 4.8.1. Attackers can inject arbitrary HTML or JavaScript into review objectives, which executes when other users view the affected review.
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
< 4.8.1
FisheyeApplication
< 4.8.1CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Fisheye or Crucible versionLog into the admin interface and navigate to the 'About' or 'System Info' page, or check the footer of any Fisheye/Crucible page for the version numberAffected if The displayed version is lower than 4.8.1 (for example, 4.8.0, 4.7.x, or earlier)
-
Confirm the product includes review objectivesNavigate to any code review in Fisheye or Crucible and look for the 'Objectives' section in the review details panelAffected if The review objectives feature is present and accessible in your installation (this feature exists in all standard installations)
-
Inspect review objectives for suspicious contentOpen existing reviews and examine the objectives field for any HTML tags, script elements, or JavaScript event handlers (onclick, onerror, onload, etc.)Affected if Any review objective contains raw HTML tags, script elements, or JavaScript code (such as <script>, <img src=x onerror=>, or javascript: URLs)
-
Check browser developer console for XSS warningsWhen viewing reviews with objectives, open the browser console and look for any security warnings or blocked script executionsAffected if The browser blocks or warns about script execution from objectives content
You are affected if your installed Fisheye or Crucible version is below 4.8.1 and you have reviews containing unsanitized HTML or JavaScript in the objectives field.
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.
From vendor data4.8.1
Upgrade Atlassian Fisheye and Crucible to version 4.8.1 or later to patch the XSS vulnerability in the review objectives feature.
Fix this in Crucible
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-4013 — 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-2020-4013 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