CrucibleApplication · Atlassian
CVE-2017-9511
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 MultiPathResource class in Atlassian Fisheye and Crucible, before version 4.4.1 allows anonymous remote attackers to read arbitrary files via a path traversal vulnerability when Fisheye or Crucible is running on the Microsoft Windows operating system.
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 confidenceThe MultiPathResource class in Atlassian Fisheye and Crucible contains a path traversal vulnerability allowing anonymous remote attackers to read arbitrary files on Windows systems due to insufficient input validation of file paths.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 Fisheye or Crucible versionAccess the application admin interface and navigate to 'About' or 'System Info', or check the version displayed on the login page. Alternatively, examine the JAR file names in the application installation directory or check the bundled version manifest.Affected if The displayed version number is 4.4.0 or any version lower than 4.4.0
-
Determine the host operating systemCheck the operating system where Fisheye or Crucible is installed by running 'systeminfo' on Windows or 'uname -a' on Unix/Linux, or check the system properties in the Control Panel.Affected if The application is running on a Windows-based host (the vulnerability specifically affects Windows systems)
-
Verify web interface accessibilityAttempt to access the Fisheye/Crucible web URL from a browser or using a tool like curl: curl -I http://<hostname>:<port>/ - where <port> is typically 8060 for Crucible or 8080 for Fisheye.Affected if The web interface responds to requests, indicating the vulnerable component is network-accessible
-
Check for anonymous access configurationReview the application configuration files (typically in the FISHEYE_INST/config.xml or similar) to determine if anonymous/unauthenticated access is permitted, or attempt to access restricted endpoints without credentials.Affected if Anonymous access is enabled, as the vulnerability allows unauthenticated attackers to exploit the path traversal
-
Confirm MultiPathResource endpoint exposureAttempt a benign path traversal test against the application by making a request with '../' sequences to a suspected endpoint, or review server logs for suspicious path traversal patterns in access logs.Affected if Requests containing '../' sequences are processed without being blocked or sanitized, indicating the vulnerability is present
If Fisheye or Crucible version 4.4.0 or earlier is running on Windows with the web interface accessible to anonymous users, the environment is affected by this path traversal vulnerability.
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 Fisheye/Crucible version 4.4.1 or later, or implement strict input validation to block path traversal sequences (../) in requests.
Fix this in Crucible
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9511 — 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-9511 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