CrucibleApplication · Atlassian
CVE-2018-13398
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 administrative smart-commits resource in Atlassian Fisheye and Crucible before version 4.5.4 allows remote attackers to modify smart-commit settings 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 confidenceThis is a CSRF vulnerability in Atlassian Fisheye and Crucible affecting the administrative smart-commits resource. Remote attackers can craft malicious requests to modify smart-commit settings without the administrator's knowledge, due to missing CSRF protections. The vulnerability exists in versions before 4.5.4.
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.4
FisheyeApplication
< 4.5.4CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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.
-
Confirm Atlassian Fisheye or Crucible installationIdentify if Fisheye or Crucible is running in your environment by checking for the application process, web interface, or installation directory. Look for typical installation paths such as /opt/atlassian/fisheye or C:\atlassian\fisheye on Windows.Affected if The product is installed and accessible on the network
-
Check installed version numberAccess the About page in the Fisheye/Crucible admin interface (typically at /admin/about.do) or check the version file in the installation directory (often VERSION.txt or displayed on startup). Compare the version to 4.5.4.Affected if The installed version is earlier than 4.5.4 (e.g., 4.5.0, 4.5.1, 4.5.2, 4.5.3, or any 4.4.x release)
-
Verify smart-commits feature is enabledNavigate to the admin section of the Fisheye/Crucible interface and check the smart-commits configuration page. Look for settings related to smart-commit commands (e.g., #review, #comment, #close) in the repository settings.Affected if Smart-commits are enabled for any repository in the instance
-
Confirm administrative interface is network-accessibleCheck if the /admin/ endpoint of your Fisheye/Crucible installation is reachable from network locations. Verify whether the admin console requires authentication and is not restricted to localhost only.Affected if The administrative interface is exposed to network access rather than localhost only
You are affected if Fisheye or Crucible version is below 4.5.4 AND smart-commits are enabled AND the admin interface is accessible, as this combination allows remote attackers to forge requests to modify smart-commit settings.
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.4
Upgrade Atlassian Fisheye and Crucible to version 4.5.4 or later, which contains the CSRF protection fix for the smart-commits endpoint.
Fix this in Crucible
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13398 — 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-2018-13398 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