CrucibleApplication · Atlassian
CVE-2017-9509
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 file upload resource in Atlassian Crucible before version 4.4.1 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability through the charset of a previously uploaded file.
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 confidenceAtlassian Crucible before version 4.4.1 contains a stored cross-site scripting (XSS) vulnerability in the review file upload resource. Attackers can inject malicious HTML or JavaScript through the charset parameter of a previously uploaded file. When other users view or review the affected file, the embedded script executes in their browsers.
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.4.0
FisheyeApplication
<= 4.4.0CVSS 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.0/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 installed Atlassian productCheck the application UI header or admin console for the product name (Crucible or Fisheye) and its version number. The version is typically displayed on the footer of web pages or in the 'About' section of the admin panel.Affected if The product shows as Atlassian Crucible or Atlassian Fisheye with version 4.4.0 or lower.
-
Verify the file upload feature is accessibleConfirm that the review file upload functionality is enabled. Check if users have permission to upload files to reviews - this is typically found in the project or repository settings under review or file upload permissions.Affected if The file upload feature is enabled and users can upload files to reviews.
-
Check for uploaded review filesBrowse to existing reviews in the system and examine any files that have been attached or uploaded to reviews. Look for files listed in the review details or file diff sections.Affected if There are files uploaded to reviews in the system.
-
Inspect file metadata for charset parameterWhen viewing an uploaded file in a review, examine the file metadata or properties panel. The vulnerability exists in the charset parameter of the file resource. In a browser developer console, inspect the DOM elements surrounding the file display to see if user-supplied charset values are being rendered without proper encoding.Affected if The charset parameter from file metadata is reflected in the HTML output without sanitization when viewing review files.
You are affected if you are running Atlassian Crucible or Fisheye version 4.4.0 or earlier and users can upload files to reviews, as the charset parameter in file metadata is not being output-encoded.
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 dataUpgrade to Atlassian Crucible version 4.4.1 or later to receive the vendor patch. If immediate upgrade is not possible, implement input validation and output encoding on file metadata fields, particularly the charset parameter.
Fix this in Crucible
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9509 — 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-9509 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