CVE-2019-20430

HIGHNVD 7.57.5—

7.5

In the Lustre file system before 2.12.3, the mdt module has an LBUG panic (via a large MDT Body eadatasize field) due to the lack of validation for specific fields of packets sent by a client.

CVSS v3: 7.5
EG Score: 7.5(medium)
EPSS: 71.6%
KEV: Not listed

Published

January 27, 2020

Last Modified

November 21, 2024

References (8)

cve@mitrehttp://lustre.org/
cve@mitrehttp://wiki.lustre.org/Lustre_2.12.3_Changelog
cve@mitrehttps://jira.whamcloud.com/browse/LU-12602
cve@mitrehttps://review.whamcloud.com/#/c/36208/
af854a3a-2127-422b-91ae-364da2661108http://lustre.org/
af854a3a-2127-422b-91ae-364da2661108http://wiki.lustre.org/Lustre_2.12.3_Changelog
af854a3a-2127-422b-91ae-364da2661108https://jira.whamcloud.com/browse/LU-12602
af854a3a-2127-422b-91ae-364da2661108https://review.whamcloud.com/#/c/36208/

Weakness Classification(2)

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

Data Freshness Timeline

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

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-27 08:39 UTCEG score recompute
2026-05-27 08:39 UTCGHSA enrichment
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2019-20430?

CVE-2019-20430 is a high vulnerability published on January 27, 2020. In the Lustre file system before 2.12.3, the mdt module has an LBUG panic (via a large MDT Body eadatasize field) due to the lack of validation for specific fields of packets sent by a client.

When was CVE-2019-20430 disclosed?

CVE-2019-20430 was first published in the National Vulnerability Database on January 27, 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-2019-20430 actively exploited?

CVE-2019-20430 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 71.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2019-20430?

CVE-2019-20430 has a CVSS v3 base score of 7.5 (NVD).

How do I remediate CVE-2019-20430?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-20430, 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-2019-20430

Explore →

Is Your Infrastructure Affected by CVE-2019-20430?

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

Start Free Scan →Browse All CVEs

CVE-2019-20430

📅 Published

🔄 Last Modified

🔗 References (8)

Weakness Classification(2)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-20430?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (8)

Frequently asked(5)

Related CVEs(same CWE)