CrucibleApplication · Atlassian
CVE-2017-18034
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 source browse resource in Atlassian Fisheye and Crucible before version 4.5.1 and 4.6.0 allows allows remote attackers that have write access to an indexed repository to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability in via a specially crafted repository branch name when trying to display deleted files of the branch.
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 confidenceThis is a stored XSS vulnerability in Atlassian Fisheye and Crucible where remote attackers with write access to an indexed repository can inject malicious HTML or JavaScript via specially crafted repository branch names. The payload executes when users browse deleted files of that branch through the source browse resource.
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.5.1= 4.6.0
FisheyeApplication
< 4.5.1= 4.6.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 Fisheye/Crucible versionLog into the Fisheye/Crucible admin console and navigate to the 'About' or 'System Information' page, or check the version banner in the footer of the web interfaceAffected if The installed version is less than 4.5.1 or exactly 4.6.0
-
Locate indexed repositoriesIn the admin interface, go to the repository configuration section and list all repositories configured for indexingAffected if There are indexed repositories configured in the system
-
Check write access to indexed repositoriesReview the permission settings for each indexed repository to determine which users or groups have commit/branch creation write accessAffected if Untrusted users or groups have write access to indexed repositories
-
Inspect branch names for malicious payloadsQuery the repository for all branch names and inspect them for suspicious patterns such as HTML tags (<script>, <img>, <iframe>), JavaScript event handlers (onerror, onload), or unusual encoded charactersAffected if Any branch names contain HTML, JavaScript, or encoded characters that could be XSS payloads
You are affected if your Fisheye/Crucible version is less than 4.5.1 or exactly 4.6.0 AND you have indexed repositories with write access enabled, particularly if any branch names contain suspicious HTML or script content.
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.5.1
Upgrade to Fisheye/Crucible version 4.5.1 or 4.6.0 or later which contains the fix for this XSS vulnerability. Until then, limit write access to indexed repositories to trusted users only.
Fix this in Crucible
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.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 $2,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18034 — 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-18034 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