Vulnerability record · CVE-2020-14179 · published 21 September 2020
CVE-2020-14179: Atlassian Jira Server and Data Center information disclosure via QueryComponent endpoint
Atlassian · Jira Data Center
Jira Server and Data Center expose custom field names and custom SLA names through the /secure/QueryComponent!Default.jspa endpoint without requiring authentication. The flaw affects versions before 8.5.8 and 8.6.0 through 8.11.1, and it matters because it leaks internal configuration metadata to any remote user.
Description
Affected versions of Atlassian Jira Server and Data Center allow remote, unauthenticated attackers to view custom field names and custom SLA names via an Information Disclosure vulnerability in the /secure/QueryComponent!Default.jspa endpoint. The affected versions are before version 8.5.8, and from version 8.6.0 before 8.11.1.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Automated analysis
medium priorityThe flaw is unauthenticated and remotely reachable with a very high EPSS score, but it only discloses limited configuration metadata and has no confirmed in-the-wild exploitation or KEV listing.
What it is
Jira Server and Data Center expose custom field names and custom SLA names through the /secure/QueryComponent!Default.jspa endpoint without requiring authentication. The flaw affects versions before 8.5.8 and 8.6.0 through 8.11.1, and it matters because it leaks internal configuration metadata to any remote user.
Impact
An unauthenticated attacker can read custom field names and custom SLA names, which may reveal internal workflows, service commitments, or naming conventions useful for further targeting. The direct impact is limited to information disclosure, not code execution or data modification.
Attack surface
The endpoint is reachable over the network via HTTP(S) and requires no authentication or user interaction, as reflected in the CVSS vector AV:N/AC:L/PR:N/UI:N. Any remote client that can reach the Jira instance can query it.
Exploitation
The record shows no CISA KEV listing and no ransomware association, but EPSS is very high at 0.76042 (99.5th percentile), indicating elevated predicted exploitation activity. The only references are vendor advisories, so no public exploit code is confirmed by this record.
What to do
- Upgrade Jira Server and Data Center to version 8.5.8 or later, or to 8.11.1 or later for the 8.6.0+ branch.
- If immediate upgrade is not possible, restrict network access to the /secure/QueryComponent!Default.jspa endpoint using a reverse proxy or WAF rule.
- Require authentication at the perimeter for Jira administrative and configuration endpoints where feasible.
- Monitor vendor advisories for backported fixes if you run an unsupported or pinned version.
Detection
- Search web access logs for requests to /secure/QueryComponent!Default.jspa, especially from unauthenticated or unexpected source IPs.
- Alert on high-volume or automated access to that endpoint from a single client.
- Correlate endpoint access with subsequent reconnaissance or enumeration activity against the Jira instance.
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 |
|---|---|
| https://jira.atlassian.com/browse/JRASERVER-71536 | Issue TrackingVendor Advisory |
| https://jira.atlassian.com/browse/JRASERVER-71536 | Issue TrackingVendor Advisory |
Track CVE-2020-14179 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-2020-14179), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.