H2O Vulnerable to Denial of Service (DoS) and File Write
CVE-2024-10572 · GHSA-wjpv-64v2-2qpq · published 2025-03-20 · updated 2025-10-15
- Severity
- High
- CVSS score
- 7.5
- Chance of exploitation (EPSS)
- 0.69%
- Fixed in
- No fix yet
- Exploitation Public proof of concept
- Automatable Yes
- Technical impact Partial
- CISA SSVC
In h2oai/h2o-3 version 3.46.0.1, the run_tool command exposes classes in the water.tools package through the ast parser. This includes the XGBoostLibExtractTool class, which can be exploited to shut down the server and write large files to arbitrary directories, leading to a denial of service.
No fixed release is listed yet for h2o. Follow the source advisory for updates, and until one ships:
General guidance from ShieldPi, not a vendor fix
- Command or code injection. Remove or disable the affected server or tool, or run it in a sandbox with no secrets in its environment.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| h2o | PyPI | >= 3.34.0.1, <= 3.46.0.1 | No fix yet |
- CriticalUnauthenticated Remote Code Execution in Langflow via Public Flow Build EndpointlangflowExploited
- CriticalRay is vulnerable to Critical RCE via Safari & Firefox Browsers through DNS Rebinding AttackrayExploited
- CriticalLangflow Unauth RCElangflow, langflow-baseExploited
- HighLiteLLM: Authenticated command execution via MCP stdio test endpointslitellmExploited
- CriticalMLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifacmlflow
- CriticalAgno: Arbitrary code execution via `eval()` on `field_type` in `FunctionCall`agno
- CriticalH2O has an External Control of File Name or Path vulnerabilityh2o
- CriticalH2O affected by a deserialization vulnerabilityh2o
- CriticalH2O Deserialization of Untrusted Data Vulnerabilityh2o
- CriticalH2O.ai H2O vulnerable to deserialization attacks via a JDBC Connection URLh2o
- CriticalExternal Control of File Name or Path in h2oai/h2o-3h2o
- HighH2O Vulnerable to Arbitrary File Overwrite via File Exporth2o
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.