CrucibleApplication · Atlassian
CVE-2020-29446
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 · uneditedAffected versions of Atlassian Fisheye & Crucible allow remote attackers to browse local files via an Insecure Direct Object References (IDOR) vulnerability in the WEB-INF directory. The affected versions are before version 4.8.5.
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 Fisheye & Crucible versions before 4.8.5 contain an Insecure Direct Object Reference (IDOR) vulnerability that allows remote attackers to browse local files in the WEB-INF directory. This could expose sensitive application files, configuration data, or source code.
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.5
FisheyeApplication
< 4.8.5CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 if Fisheye or Crucible is installedCheck for running processes matching 'fisheye' or 'crucible', or look for the application in common installation directories such as /opt/atlassian/fisheye, /opt/atlassian/crucible, or C:\Atlassian\ on WindowsAffected if The application is installed and running as a service or process
-
Determine the installed versionAccess the application's admin interface and navigate to the 'About' or 'Version' page, or check the version file in the installation directory (typically named VERSION, version.txt, or shown in the startup logs)Affected if The version is lower than 4.8.5 for either Fisheye or Crucible
-
Verify the application is network accessibleConfirm the Fisheye or Crucible web interface is reachable over HTTP/HTTPS on the configured port (default is 8060 for Fisheye, 8000 for Crucible)Affected if The application is exposed on a network or the internet, making the IDOR vulnerability exploitable remotely
-
Confirm WEB-INF directory is accessibleAttempt to access the vulnerable endpoint by requesting a path such as /res/WEB-INF/web.xml or similar file paths within the WEB-INF directory structure without authenticationAffected if The server returns file contents from the WEB-INF directory without requiring authentication, indicating the IDOR vulnerability is present
A user is affected if Fisheye or Crucible version below 4.8.5 is installed and the application is network-accessible, allowing unauthenticated access to WEB-INF directory files.
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.5
Upgrade to Fisheye & Crucible version 4.8.5 or later to resolve the IDOR vulnerability.
Fix this in Crucible
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-29446 — 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-29446 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