CVE-2020-1963

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 4.7%, top 11% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 5%CVSS: 9.1Exploit: NoneExposed: 0

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

Apache Ignite uses H2 database to build SQL distributed execution engine. H2 provides SQL functions which could be used by attacker to access to a filesystem.

CVSS v3
9.1
EG Score
9.1(medium)
EPSS
91.2%
KEV
Not listed

Published

June 3, 2020

Last Modified

November 21, 2024

References (20)

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.ignite:ignite-core1.0.0 ... 2.8.0 (24 versions)2.8.1

Weakness Classification(1)

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

Frequently asked(5)

What is CVE-2020-1963?
CVE-2020-1963 is a critical vulnerability published on June 3, 2020. Apache Ignite uses H2 database to build SQL distributed execution engine. H2 provides SQL functions which could be used by attacker to access to a filesystem.
When was CVE-2020-1963 disclosed?
CVE-2020-1963 was first published in the National Vulnerability Database on June 3, 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-1963 actively exploited?
CVE-2020-1963 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 91.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-1963?
CVE-2020-1963 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2020-1963?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-1963, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-1963

Explore →

Is Your Infrastructure Affected by CVE-2020-1963?

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