Browse / AI Framework and Platform Flaws / CVE-2024-45758
H2O.ai H2O vulnerable to deserialization attacks via a JDBC Connection URL
- 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.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- EPSS
- 0.9% chance of exploitation in 30 days
How it works, in short
The import endpoint accepts a caller-chosen JDBC URL, and crafted driver parameters trigger deserialization, file reads and command execution on the server. (Our summary, written by a model. The source text is below.)
Details
H2O.ai H2O through 3.46.0.4 allows attackers to arbitrarily set the JDBC URL, leading to deserialization attacks, file reads, and command execution. Exploitation can occur when an attacker has access to post to the ImportSQLTable URI with a JSON document containing a connection_url property with any typical JDBC Connection URL attack payload such as one that uses queryInterceptors.
References
- https://nvd.nist.gov/vuln/detail/CVE-2024-45758
- https://github.com/h2oai/h2o-3/issues/16425
- https://github.com/h2oai/h2o-3/issues/16622
- https://github.com/h2oai/h2o-3/pull/16624
- https://github.com/h2oai/h2o-3/commit/f714edd6b8429c7a7211b779b6ec108a95b7382d
- https://gist.github.com/AfterSnows/c24ca3c26dc89ab797e610e92a6a9acb
- https://github.com/h2oai/h2o-3
- https://github.com/pypa/advisory-database/tree/main/vulns/h2o/PYSEC-2026-352.yaml
- https://pypi.org/project/h2o
- https://spear-shield.notion.site/Unauthenticated-Remote-Code-Execution-via-Unrestricted-JDBC-Connection-87a958a4874044199cbb86422d1f6068
Source: GitHub Advisory Database, used under CC BY 4.0.