Vulnerability record · CVE-2019-8442 · published 22 May 2019
CVE-2019-8442: Jira path check flaw exposes META-INF webroot files
Atlassian · Jira
The CachingResourceDownloadRewriteRule class in Jira Server performs a lax path access check, letting remote attackers read files under the META-INF directory of the Jira webroot. Versions before 7.13.4, 8.0.0 through 8.0.3, and 8.1.0 are affected. Exposed META-INF content can reveal build and dependency metadata useful for further attacks.
Description
The 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Automated analysis
high priorityUnauthenticated remote file disclosure with a high CVSS score and very high EPSS percentile warrants prompt patching despite no KEV listing.
What it is
The CachingResourceDownloadRewriteRule class in Jira Server performs a lax path access check, letting remote attackers read files under the META-INF directory of the Jira webroot. Versions before 7.13.4, 8.0.0 through 8.0.3, and 8.1.0 are affected. Exposed META-INF content can reveal build and dependency metadata useful for further attacks.
Impact
An unauthenticated attacker gains read access to files in the Jira webroot META-INF directory, leaking configuration and dependency information. There is no integrity or availability impact; the loss is confidentiality only.
Attack surface
Reachable over the network via HTTP requests to the Jira web application, per the CVSS vector AV:N/AC:L/PR:N/UI:N. No authentication or user interaction is required.
Exploitation
Not listed in CISA KEV and no public exploit tag appears in the references, but EPSS is 0.59832 (99th percentile), indicating elevated predicted exploitation activity.
What to do
- Upgrade Jira Server to 7.13.4, 8.0.4, or 8.1.1 or later, which contain the fix.
- If immediate upgrade is not possible, restrict network access to the Jira instance to trusted users and networks.
- Block or filter requests that traverse into META-INF paths at the reverse proxy or WAF.
- Review Jira webroot and META-INF contents for sensitive build or dependency data that could aid attackers.
Detection
- Search web and proxy logs for requests containing META-INF in the URL path.
- Alert on encoded traversal sequences such as %2e%2e or ..%2f targeting Jira endpoints.
- Monitor for anomalous unauthenticated access to static or resource download URLs on the Jira host.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Affected products
2 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| http://www.securityfocus.com/bid/108460 | Broken Link |
| https://jira.atlassian.com/browse/JRASERVER-69241 | Issue TrackingVendor Advisory |
| http://www.securityfocus.com/bid/108460 | Broken Link |
| https://jira.atlassian.com/browse/JRASERVER-69241 | Issue TrackingVendor Advisory |
Track CVE-2019-8442 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2019-8442), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.