CrucibleApplication · Atlassian
CVE-2017-14591
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 · uneditedAtlassian Fisheye and Crucible versions less than 4.4.3 and version 4.5.0 are vulnerable to argument injection through filenames in Mercurial repositories, allowing attackers to execute arbitrary code on a system running the impacted software.
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 confidenceArgument injection vulnerability in Atlassian Fisheye and Crucible allows attackers to execute arbitrary code by crafting malicious filenames in Mercurial repositories. The vulnerability stems from improper sanitization of filenames passed as arguments to Mercurial commands.
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.3= 4.5.0
FisheyeApplication
< 4.4.3= 4.5.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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
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 if Fisheye or Crucible is installedCheck for running processes named 'fisheye' or 'crucible', or look for their installation directories (typically in /opt/atlassian/fisheye or /opt/atlassian/crucible on Linux, or C:\Program Files\Atlassian\ on Windows)Affected if Fisheye or Crucible software is present on the system
-
Determine the installed versionCheck the version file in the installation directory (e.g., 'fisheye_version' or 'crucible_version' file), or log into the admin dashboard and view the 'About' or 'System Info' pageAffected if Version is less than 4.4.3 or exactly 4.5.0
-
Check if Mercurial repositories are configuredReview the repository configuration in Fisheye/Crucible admin interface, or inspect the config.xml file in the FishEye/Crucible data directory for <repo type='mercurial'> entries, or look for .hg directories in monitored pathsAffected if Mercurial repositories are being monitored and the product version is vulnerable
A user is affected if they have Fisheye or Crucible installed with version less than 4.4.3 or exactly 4.5.0, and they have Mercurial repositories configured.
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.
dbcve · scoped4.4.3
Upgrade Atlassian Fisheye and Crucible to version 4.4.3 or later (or any version beyond 4.5.0) to remediate this vulnerability.
4.4.3 or later
- 1. Back up your current Fisheye/Crucible installation and data directories
- 2. Download Atlassian Fisheye/Crucible version 4.4.3 or later from the official Atlassian website
- 3. Stop the Fisheye/Crucible service
- 4. Install the new version following Atlassian upgrade documentation
- 5. Restore your data from the backup if needed
- 6. Start the Fisheye/Crucible service
- 7. Verify the installation by checking the About page shows the new version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Crucible
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14591 — 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-14591 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