CrucibleApplication · Atlassian
CVE-2018-13399
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 Microsoft Windows Installer for Atlassian Fisheye and Crucible before version 4.6.1 allows local attackers to escalate privileges because of weak permissions on the installation directory.
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 Microsoft Windows Installer for Atlassian Fisheye and Crucible before version 4.6.1 creates the installation directory with overly permissive file system permissions, allowing local unprivileged users to modify executable files, DLLs, or configuration files that execute with elevated privileges, resulting in local privilege escalation.
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.6.1
FisheyeApplication
< 4.6.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Fisheye or Crucible versionCheck the version file in the installation directory (e.g., fisheye/crucible installation folder) or use Windows Programs and Features to view the installed version of Fisheye or CrucibleAffected if The installed version is below 4.6.1
-
Locate the installation directoryFind the default installation path, typically C:\Atlassian\ApplicationData\Fisheye or C:\Atlassian\ApplicationData\Crucible, or check the installation path from the application properties in Windows Programs and FeaturesAffected if The installation directory exists and contains Fisheye or Crucible files below version 4.6.1
-
Verify file permissions on the installation directoryRight-click the installation folder, go to Properties > Security, and check which users and groups have Write or Modify permissions. Alternatively, use icacls command from an elevated command prompt: icacls "<installation_path>"Affected if Non-administrator users or the Users group have Write, Modify, or Full Control permissions on the installation directory
-
Check for modifiable executables or DLLs in the installation directoryReview the permissions on key files in the installation directory such as .exe, .dll, and configuration files (e.g., config.xml, run.bat, .jar files). Use icacls to list effective permissions for a standard user accountAffected if Standard user accounts can modify executables, DLLs, or configuration files that are executed by the service
-
Determine if the service runs with elevated privilegesOpen Services (services.msc), locate the Fisheye or Crucible service, right-click and view Properties, check the Log On account. Also check if the service runs as LocalSystem or an administrator accountAffected if The service runs as LocalSystem or another account with administrator privileges
You are affected if Fisheye or Crucible version below 4.6.1 is installed and the installation directory grants write/modify permissions to non-administrator users, allowing them to modify files that execute with elevated privileges.
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.6.1
Upgrade to Fisheye/Crucible version 4.6.1 or later which contains corrected permission settings, or manually restrict access to the installation directory to administrator-only accounts.
Fix this in Crucible
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13399 — 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-13399 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