JiraApplication · Atlassian
CVE-2019-8442
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 CachingResourceDownloadRewriteRule class in Jira before version 7.13.4, and from version 8.0.0 before version 8.0.4, and from version 8.1.0 before version 8.1.1 allows remote attackers to access files in the Jira webroot under the META-INF directory via a lax path access check.
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 confidenceA path traversal vulnerability in Jira's CachingResourceDownloadRewriteRule class allows remote unauthenticated attackers to access files within the META-INF directory of the webroot via a lax path access check. This enables arbitrary file read access with high confidentiality impact.
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
JiraApplication
< 7.13.4
Jira ServerApplication
>= 8.0.0, < 8.0.4>= 8.1.0, < 8.1.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Determine Jira versionCheck the installed Jira version from the application admin interface (About Jira) or by examining the atlassian-jira/WEB-INF/classes/com/atlassian/jira/version.properties fileAffected if The version is < 7.13.4 OR >= 8.0.0 and < 8.0.4 OR >= 8.1.0 and < 8.1.1
-
Identify CachingResourceDownloadRewriteRule classExamine the Jira web application archive for the presence of the CachingResourceDownloadRewriteRule class in the classpathAffected if The vulnerable class exists in the atlassian-jira/WEB-INF/lib or classes directory
-
Test path traversal to META-INFSend an HTTP GET request to the Jira base URL with a path such as /s/../META-INF/ or similar path traversal sequences targeting the META-INF directoryAffected if The server returns file contents from within the META-INF directory or responds with a 200 OK instead of blocking the request with a 403 or 404
-
Verify unauthenticated access exposureDetermine if the Jira instance is accessible over the network without authentication (not behind a VPN, not requiring login for base URL access)Affected if The Jira web interface is reachable by unauthenticated remote users
A user is affected if their Jira installation version falls within the vulnerable ranges AND the vulnerable CachingResourceDownloadRewriteRule class is present AND the META-INF directory is accessible via path traversal from an unauthenticated network position.
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 data7.13.48.0.48.1.1
Upgrade Jira to version 7.13.4, 8.0.4, 8.1.1, or later to patch the vulnerable CachingResourceDownloadRewriteRule class. If immediate upgrade is not possible, consider restricting access at the application or proxy layer.
Fix this in Jira
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8442 — 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-8442 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