Jira Data CenterApplication · Atlassian
CVE-2019-20419
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 Jira Server and Data Center allow remote attackers to execute arbitrary code via a DLL hijacking vulnerability in Tomcat. The affected versions are before version 8.5.5, and from version 8.6.0 before 8.7.2.
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 confidenceAffected versions of Atlassian Jira Server and Data Center contain a DLL hijacking vulnerability in the embedded Tomcat server. Remote attackers can execute arbitrary code by placing a malicious DLL in a location where Tomcat loads DLLs, likely in the working directory or a path where Jira's Tomcat looks for native libraries.
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
Jira Data CenterApplication
< 8.5.5>= 8.6.0, < 8.7.2
Jira ServerApplication
< 8.5.5>= 8.6.0, < 8.7.2CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Jira versionAccess Jira administration and navigate to Troubleshooting and support > System info, or query the /rest/api/2/serverInfo endpoint, or check the build.json file in the webapp directoryAffected if The version falls within < 8.5.5 or >= 8.6.0 and < 8.7.2
-
Verify Tomcat embedded library pathLocate the atlassian-jira directory and identify the Tomcat libraries folder (typically atlassian-jira/WEB-INF/ or a bundled Tomcat directory)Affected if The embedded Tomcat component exists in the installation (standard for affected versions)
-
Inspect Jira working directory for unauthorized DLLsIdentify the Jira process working directory (check process properties or Jira configuration for java.io.tmpdir or the startup working directory) and list all DLL files presentAffected if Any unexpected or suspicious DLL files are found in the working directory that were not shipped with Jira or Tomcat
-
Check Tomcat native library paths for foreign DLLsExamine directories where Tomcat loads native libraries, including the Jira working directory, Tomcat bin directory, and any paths configured in the java.library.path system propertyAffected if Unrecognized DLL files exist in these paths that could be loaded by the Tomcat process
A user is affected if their Jira Server or Data Center version is 8.5.x prior to 8.5.5, or 8.6.0 through 8.7.1, and an attacker can place a malicious DLL in the working directory or a Tomcat DLL loading path.
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 data8.5.58.7.2
Upgrade Jira Server or Data Center to version 8.7.2 or later (or 8.5.5 if staying on the 8.5.x branch) to resolve the vulnerable Tomcat component.
Fix this in Jira Data Center
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing6.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 $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20419 — 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-2019-20419 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