Browse / AI Framework and Platform Flaws / CVE-2024-10553
H2O Deserialization of Untrusted Data Vulnerability
- Class
- AI Framework and Platform Flaws (filed by a model that read the advisory)
- Technique
- Code and command execution
- Affected
- ai.h2o:h2o-core, h2o (Maven)
- CVSS
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 1.6% chance of exploitation in 30 days
How it works, in short
Unauthenticated JDBC URLs passed to the import endpoints reach driver connection code, where untrusted deserialisation runs when a database driver is on the classpath. (Our summary, written by a model. The source text is below.)
Details
A vulnerability in the h2oai/h2o-3 REST API versions 3.46.0.4 allows unauthenticated remote attackers to execute arbitrary code via deserialization of untrusted data. The vulnerability exists in the endpoints POST /99/ImportSQLTable and POST /3/SaveToHiveTable, where user-controlled JDBC URLs are passed to DriverManager.getConnection, leading to deserialization if a MySQL or PostgreSQL driver is available in the classpath. This issue is fixed in version 3.46.0.6.
References
- https://nvd.nist.gov/vuln/detail/CVE-2024-10553
- https://github.com/h2oai/h2o-3/commit/ac1d642b4d86f10a02d75974055baf2a4b2025ac
- https://github.com/h2oai/h2o-3
- https://github.com/pypa/advisory-database/tree/main/vulns/h2o/PYSEC-2026-351.yaml
- https://huntr.com/bounties/e6f550dd-eda2-428c-a740-ed8f893a084b
- https://pypi.org/project/h2o
Source: GitHub Advisory Database, used under CC BY 4.0.