Skip to main content
Mallory
HighVulnerability

CVE-2019-8442: Path Traversal in Jira CachingResourceDownloadRewriteRule

Published May 22, 2019 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3.1
EPSS59.8%99th percentile
CISA KEVNoNot listed
In the wildReported198 exploitation records in Mallory
Vendor
Atlassian
IdentifiersCVE-2019-8442CWE-22

CVE-2019-8442 is a path traversal vulnerability in the CachingResourceDownloadRewriteRule class of Jira Data Center. Due to insufficient path access checks, remote attackers can access files located in the Jira webroot under the META-INF directory. The vulnerability affects Jira versions before 7.13.4, 8.0.0 before 8.0.4, and 8.1.0 before 8.1.1. The flaw is classified as a file inclusion and injection issue, introduced in Jira version 7.13.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to access files in the Jira webroot under the META-INF directory. This could lead to sensitive information disclosure, depending on the contents of the exposed files. The vulnerability does not allow arbitrary file access outside the intended directory, but still poses a risk of information leakage.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, restrict network access to the Jira instance to trusted users only. Monitor access logs for suspicious requests targeting the META-INF directory. Consider applying web application firewall (WAF) rules to block attempts to access sensitive paths.

Remediation

Patch, then assume compromise.

Upgrade Jira to version 7.13.4, 8.0.4, or 8.1.1 or later. Atlassian has released patches that address the insufficient path access check in the CachingResourceDownloadRewriteRule class, preventing unauthorized file access.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AtlassianJiraapplication
AtlassianJira Serverapplication
FAQ

Frequently asked questions

Is CVE-2019-8442 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2019-8442?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2019-8442.
Is there a patch for CVE-2019-8442?
Upgrade Jira to version 7.13.4, 8.0.4, or 8.1.1 or later. Atlassian has released patches that address the insufficient path access check in the CachingResourceDownloadRewriteRule class, preventing unauthorized file access.
What products are affected by CVE-2019-8442?
Atlassian Jira and Atlassian Jira Server.
How severe is CVE-2019-8442?
CVE-2019-8442 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 59.8% (99th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.