CVE-2024-6960 json
H2O deserializes ML models without filtering, potentially allowing execution of malicious code
published 2024-07-21 2 y ago modified 2026-06-17 4 mo ago also GHSA-w36w-948j-xhfw , EUVD-2024-2430
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 52%
- public exploits
- 0
- none known
Summary
The H2O machine learning platform uses "Iced" classes as the primary means of moving Java Objects around the cluster. The Iced format supports inclusion of serialized Java objects. When a model is deserialized, any class is allowed to be deserialized (no class whitelist). An attacker can construct a crafted Iced model that uses Java gadgets and leads to arbitrary code execution when imported to the H2O platform.
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
0.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | ai.h2o:h2o-core | <=3.46.0.4 |
no fix listed |
Affected products
- mvnrepository h2o-core
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
research.jfrog.com
/vulnerabilities/h2o-model-deserialization-rce-jfsa-2024-001035518/
third-party-advisory
-
mvnrepository.com
/artifact/ai.h2o/h2o-core
product, web
-
nvd.nist.gov
/vuln/detail/CVE-2024-6960
advisory
-
github.com
/h2oai/h2o-3
package
-
research.jfrog.com
/vulnerabilities/h2o-model-deserialization-rce-jfsa-2024-001035518
web
Sources
- CVE List CVE-2024-6960
- GitHub Advisory GHSA-w36w-948j-xhfw
- NVD CVE-2024-6960
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.