CVE-2024-5979

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2024-06-27. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

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

In h2oai/h2o-3 version 3.46.0, the run_tool command in the rapids component allows the main function of any class under the water.tools namespace to be called. One such class, MojoConvertTool, crashes the server when invoked with an invalid argument, causing a denial of service.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
50
EG Risk 50/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 27, 2024

Last Modified

October 15, 2025

References (2)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
piph2o—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
h2o3.10.0.10 ... 3.44.0.3 (111 versions)
  • every version through 3.46.0: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 88 of 176 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 12 repeat rows among the latest 100 are merged into the row they repeat. The 88 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 21:02 UTCEG score recompute
  2. 2026-10-11 15:53 UTCEG score recompute
  3. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  4. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  5. 2026-10-10 15:25 UTCOSV refresh
  6. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  7. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  8. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  9. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  10. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  11. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  12. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  13. 2026-10-02 16:27 UTCEG score recompute
  14. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  15. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  16. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  17. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  18. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  19. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  20. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  21. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  22. 2026-09-21 02:06 UTCOSV refresh
  23. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  24. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  25. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.8% · 54th percentile
Show 63 more
  1. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  2. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  3. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  4. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  5. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  6. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  7. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  8. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  9. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  10. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  11. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  12. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  13. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  14. 2026-09-02 00:12 UTCOSV refresh
  15. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  16. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  17. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  18. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  19. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  20. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  21. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  22. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  23. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  24. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  25. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  26. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  27. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  28. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  29. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  30. 2026-08-16 02:35 UTCOSV refresh
  31. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  32. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  33. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  34. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  35. 2026-08-11 13:41 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  36. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  37. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  38. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  39. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  40. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  41. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  42. 2026-08-04 15:08 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  43. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  44. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  45. 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  46. 2026-07-31 20:12 UTCOSV refresh
  47. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  48. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  49. 2026-07-28 15:35 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  50. 2026-07-26 14:53 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  51. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  52. 2026-07-24 14:16 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  53. 2026-07-23 14:17 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  54. 2026-07-23 02:45 UTCEG score recompute
  55. 2026-07-22 14:07 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  56. 2026-07-21 15:23 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  57. 2026-07-20 17:07 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  58. 2026-07-19 14:30 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  59. 2026-07-19 02:28 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  60. 2026-07-18 10:03 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  61. 2026-07-16 17:02 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  62. 2026-07-15 16:57 UTCEPSS rescoreEPSS 0.8% · 52nd percentile
  63. 2026-07-15 01:59 UTCEPSS rescoreEPSS 0.8% · 51st percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-5979?
CVE-2024-5979 is a high-severity vulnerability; its CVE record was published on June 27, 2024. In h2oai/h2o-3 version 3.46.0, the run_tool command in the rapids component allows the main function of any class under the water.tools namespace to be called. One such class, MojoConvertTool, crashes the server when invoked with an invalid argument, causing a denial of service.
When was the CVE record for CVE-2024-5979 published?
The CVE record for CVE-2024-5979 was published on June 27, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2025; the record at its source may have been updated since.
Is CVE-2024-5979 actively exploited?
CVE-2024-5979 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-5979?
CVE-2024-5979 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2024-5979?
No fix for CVE-2024-5979 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-5979

Explore →

Is Your Infrastructure Affected by CVE-2024-5979?

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

Book a Demo →Browse All CVEs