dbcve.org
CrucibleApplication · Atlassian

CVE-2020-4018

HIGH · 8.8 CVSS v3.1 Published 2020-06-01
Fix available
A fix is available. Upgrade to 4.8.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
The setup resources in Atlassian Fisheye and Crucible before version 4.8.1 allows remote attackers to complete the setup process via a cross-site request forgery (CSRF) vulnerability.

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 confidence

This is a CSRF vulnerability in the setup functionality of Atlassian Fisheye and Crucible. The vulnerability allows remote attackers to trick authenticated administrators or potentially unauthenticated users into completing the setup process via forged requests, potentially allowing attackers to manipulate the initial configuration of the application.

MitigationUpgrade to Fisheye/Crucible version 4.8.1 or later, which includes CSRF protection in the setup resources.

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
Affected:< 4.8.1
FisheyeApplication
Affected:< 4.8.1

CVSS 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Fisheye or Crucible version
    Check the application version through the admin UI at 'Admin > General Settings' or by running the version command (fisheye --version or crucible --version) from the installation directory
    Affected if The version number is lower than 4.8.1 for either product
  2. Determine if setup functionality is accessible
    Attempt to access the setup endpoint at /setup/ (e.g., https://your-server:8060/setup/) or check if the initial setup wizard can be triggered or is not yet completed
    Affected if The setup page loads or setup has not been completed, indicating the vulnerable endpoint is accessible
  3. Verify CSRF protection status in configuration
    Check the application configuration file (usually config.xml in the FISHEYE_INST directory) for any CSRF-related settings or examine the HTTP responses from setup endpoints for presence of CSRF tokens
    Affected if No CSRF tokens are present in setup form submissions or the application lacks CSRF protection for setup resources

You are affected if you are running Fisheye or Crucible version below 4.8.1 AND the setup functionality is accessible or was not properly secured during initial configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 4.8.1 or later
Fixed in 4.8.1
Interim mitigation

Upgrade to Fisheye/Crucible version 4.8.1 or later, which includes CSRF protection in the setup resources.

Fix this in Crucible Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-4018 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-4018 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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