CVE-2024-38418

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-02-03. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

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

Memory corruption while parsing the memory map info in IOCTL calls.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.1%
KEV
Not listed

Published

February 3, 2025

Last Modified

February 5, 2025

References (1)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 3× in last 7d / 15× 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-23 02:38 UTCEG score recompute
  2. 2026-07-22 14:07 UTCEPSS rescore
  3. 2026-07-22 14:07 UTCEPSS rescore
  4. 2026-07-16 17:02 UTCEPSS rescore
  5. 2026-07-15 16:56 UTCEPSS rescore
  6. 2026-07-15 16:56 UTCEPSS rescore
  7. 2026-07-11 08:26 UTCEPSS rescore
  8. 2026-07-11 08:26 UTCEPSS rescore
  9. 2026-07-08 15:14 UTCEPSS rescore
  10. 2026-07-08 15:13 UTCEPSS rescore
  11. 2026-07-07 13:45 UTCEPSS rescore
  12. 2026-07-01 15:05 UTCEPSS rescore
  13. 2026-06-29 14:05 UTCEPSS rescore
  14. 2026-06-24 14:04 UTCEPSS rescore
  15. 2026-06-24 14:04 UTCEPSS rescore
  16. 2026-06-18 17:52 UTCEPSS rescore
  17. 2026-06-18 17:51 UTCEPSS rescore
  18. 2026-06-17 17:52 UTCEPSS rescore
  19. 2026-06-15 17:47 UTCEPSS rescore
  20. 2026-06-14 23:16 UTCEPSS rescore
  21. 2026-06-13 22:59 UTCEPSS rescore
  22. 2026-06-13 22:59 UTCEPSS rescore
  23. 2026-06-12 23:11 UTCEPSS rescore
  24. 2026-06-11 13:59 UTCEPSS rescore
  25. 2026-06-10 22:17 UTCEPSS rescore
Show 20 more
  1. 2026-06-10 13:21 UTCEPSS rescore
  2. 2026-06-08 14:16 UTCEPSS rescore
  3. 2026-06-07 15:24 UTCEPSS rescore
  4. 2026-06-07 15:24 UTCEPSS rescore
  5. 2026-06-06 13:46 UTCEPSS rescore
  6. 2026-06-06 13:46 UTCEPSS rescore
  7. 2026-06-05 22:46 UTCEPSS rescore
  8. 2026-06-05 22:46 UTCEPSS rescore
  9. 2026-06-05 06:09 UTCEPSS rescore
  10. 2026-06-05 06:09 UTCEPSS rescore
  11. 2026-06-04 13:11 UTCEPSS rescore
  12. 2026-06-04 13:11 UTCEPSS rescore
  13. 2026-06-02 20:12 UTCEPSS rescore
  14. 2026-06-01 13:51 UTCEPSS rescore
  15. 2026-06-01 13:51 UTCEPSS rescore
  16. 2026-05-31 22:30 UTCEPSS rescore
  17. 2026-05-31 22:30 UTCEPSS rescore
  18. 2026-05-30 12:22 UTCEG score recompute
  19. 2026-05-30 12:22 UTCGHSA enrichment
  20. 2026-05-29 13:43 UTCEPSS rescore

Frequently asked(5)

What is CVE-2024-38418?
CVE-2024-38418 is a high vulnerability published on February 3, 2025. Memory corruption while parsing the memory map info in IOCTL calls.
When was CVE-2024-38418 disclosed?
CVE-2024-38418 was first published in the National Vulnerability Database on February 3, 2025, with the most recent update on February 5, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-38418 actively exploited?
CVE-2024-38418 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-38418?
CVE-2024-38418 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-38418?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-38418, 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-2024-38418

Explore →

Is Your Infrastructure Affected by CVE-2024-38418?

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

Start Free Scan →Browse All CVEs