How severe is CVE-2020-14179?

CVE-2020-14179 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2020-14179?

Affected package information for CVE-2020-14179 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2020-14179?

No fixed version has been published for CVE-2020-14179 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2020-14179 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2020-14179, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2020-14179?

CVE-2020-14179 has an EPSS (Exploit Prediction Scoring System) score of 92.6%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Which products and versions are affected by CVE-2020-14179?

CVE-2020-14179 affects atlassian jira data center; atlassian jira server. Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2020-14179?

A Nuclei detection template exists for CVE-2020-14179, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2020-14179 published, and has it been updated?

CVE-2020-14179 was published on September 21, 2020 and was last updated on November 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2020-14179

MEDIUM

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…

Published

Sep 21, 2020

Updated

Nov 21, 2024

Affected

0 pkgs

Patched

None yet

Exploits

4 known

EPSS Exploitation Probability

via FIRST.org ↗

92.6%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

Affected Products

2 products · 4 configurations

Application

jira data centeratlassian

≥ 8.6.0 && < 8.11.1

range

Application

jira serveratlassian

≥ 8.6.0 && < 8.11.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Affected versions of Atlassian Jira Server and Data Center allow remote,…

github.comGithubJan 2021

Affected versions of Atlassian Jira Server and Data Center allow remote,…

github.comGithubDec 2023

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-14179 in your stack?

O3 detects CVE-2020-14179 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works