CVE-2020-14179

MEDIUMNVD 5.38.4
EchelonGraph scoreHIGH confidence

Score elevated to 8.4 because EPSS predicts 76% probability of exploitation within the next 30 days (top 0.5% of all CVEs). NVD baseline CVSS 5.3 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
5.3
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 76%
CISA-KEV: Not listedEPSS: 76%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
5.3
EG Score
8.4(high)
EG Risk
73(Track)
EG Risk 73/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity84% × 45%
Exploitation76% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.5%
KEV
Not listed

Published

September 21, 2020

Last Modified

November 21, 2024

References (2)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 18× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:14 UTCEPSS rescore
  2. 2026-07-23 01:49 UTCEG score recompute 3.10
  3. 2026-07-22 22:34 UTCEG score recompute
  4. 2026-07-22 14:05 UTCEPSS rescore
  5. 2026-07-21 15:22 UTCEPSS rescore
  6. 2026-07-21 15:22 UTCEPSS rescore
  7. 2026-07-20 17:04 UTCEPSS rescore
  8. 2026-07-15 16:55 UTCEPSS rescore
  9. 2026-07-13 22:27 UTCEPSS rescore
  10. 2026-07-12 05:44 UTCEPSS rescore
  11. 2026-07-09 19:06 UTCEPSS rescore
  12. 2026-07-07 13:43 UTCEPSS rescore
  13. 2026-06-30 23:20 UTCEPSS rescore
  14. 2026-06-30 23:20 UTCEPSS rescore
  15. 2026-06-28 04:54 UTCEPSS rescore
  16. 2026-06-28 04:54 UTCEPSS rescore
  17. 2026-06-25 13:47 UTCEPSS rescore
  18. 2026-06-25 13:47 UTCEPSS rescore
  19. 2026-06-24 14:03 UTCEPSS rescore
  20. 2026-06-24 14:03 UTCEPSS rescore
  21. 2026-06-23 21:31 UTCEPSS rescore
  22. 2026-06-23 21:31 UTCEPSS rescore
  23. 2026-06-21 01:57 UTCEPSS rescore
  24. 2026-06-21 01:57 UTCEPSS rescore
  25. 2026-06-18 17:50 UTCEPSS rescore
Show 19 more
  1. 2026-06-18 17:50 UTCEPSS rescore
  2. 2026-06-17 17:50 UTCEPSS rescore
  3. 2026-06-17 17:50 UTCEPSS rescore
  4. 2026-06-15 17:46 UTCEPSS rescore
  5. 2026-06-13 22:58 UTCEPSS rescore
  6. 2026-06-13 22:58 UTCEPSS rescore
  7. 2026-06-12 23:09 UTCEPSS rescore
  8. 2026-06-11 13:58 UTCEPSS rescore
  9. 2026-06-10 13:20 UTCEPSS rescore
  10. 2026-06-05 22:45 UTCEPSS rescore
  11. 2026-06-05 22:45 UTCEPSS rescore
  12. 2026-05-31 00:15 UTCEPSS rescore
  13. 2026-05-31 00:14 UTCEPSS rescore
  14. 2026-05-29 13:42 UTCEPSS rescore
  15. 2026-05-29 13:42 UTCEPSS rescore
  16. 2026-05-26 07:17 UTCEPSS rescore
  17. 2026-05-26 07:17 UTCEPSS rescore
  18. 2026-05-23 07:31 UTCEG score recompute
  19. 2026-05-23 07:31 UTCGHSA enrichment

Publicly available exploits

(3 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCmrnazu/CVE-2020-14179
    First seen Dec 3, 2023

    Sensitive data exposure via /secure/QueryComponent!Default.jspa endpoint - CVE-2020-14179

    Open source ↗
  • GitHub PoCc0brabaghdad1/CVE-2020-14179
    First seen Jan 8, 2021

    CVE-2020-14179 Scanner

    Open source ↗
  • Nucleihttp/cves/2020/CVE-2020-14179.yaml
    First seen Jan 1, 2020

    Atlassian Jira Server/Data Center <8.5.8/8.6.0 - 8.11.1 - Information Disclosure

    Open source ↗

Frequently asked(5)

What is CVE-2020-14179?
CVE-2020-14179 is a medium vulnerability published on September 21, 2020. 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…
When was CVE-2020-14179 disclosed?
CVE-2020-14179 was first published in the National Vulnerability Database on September 21, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-14179 actively exploited?
CVE-2020-14179 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-14179?
CVE-2020-14179 has a CVSS v3 base score of 5.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.4.
How do I remediate CVE-2020-14179?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-14179, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-14179

Explore →

Is Your Infrastructure Affected by CVE-2020-14179?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.