CVE-2020-14179
First published: Mon Sep 21 2020(Updated: )
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.
Credit: security@atlassian.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Atlassian Jira Data Center | <8.5.8 | |
| Atlassian Jira Data Center | >=8.6.0<8.11.1 | |
| Atlassian Jira Server | <8.5.8 | |
| Atlassian Jira Server | >=8.6.0<8.11.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the vulnerability ID for this Atlassian Jira vulnerability?
The vulnerability ID is CVE-2020-14179.
What is the severity rating of CVE-2020-14179?
The severity rating of CVE-2020-14179 is medium.
How can remote attackers exploit CVE-2020-14179 in Atlassian Jira?
Remote unauthenticated attackers can exploit CVE-2020-14179 in Atlassian Jira by viewing custom field names and custom SLA names via an Information Disclosure vulnerability in the /secure/QueryComponent!Default.jspa endpoint.
Which versions of Atlassian Jira Server and Data Center are affected by CVE-2020-14179?
Versions before 8.5.8 and from 8.6.0 to 8.11.1 of Atlassian Jira Server and Data Center are affected by CVE-2020-14179.
Is there a fix available for CVE-2020-14179?
Yes, upgrading to version 8.5.8 or higher for Atlassian Jira Server and Data Center will fix CVE-2020-14179.
- collector/nvd-index
- vendor/atlassian
- canonical/atlassian jira data center
- version/atlassian jira data center/8.6.0
- canonical/atlassian jira server
- version/atlassian jira server/8.6.0