H2O Vulnerable to Arbitrary File Overwrite via File Export
CVE-2024-6854 · GHSA-47f6-5p7h-5f3h · published 2025-03-20
- Severity
- High
- CVSS score
- 7.1
- Chance of exploitation (EPSS)
- 0.78%
- Fixed in
- No fix yet
- Exploitation Public proof of concept
- Automatable No
- Technical impact Partial
- CISA SSVC
In h2oai/h2o-3 version 3.46.0, the endpoint for exporting models does not restrict the export location, allowing an attacker to export a model to any file in the server's file structure, thereby overwriting it. This vulnerability can be exploited to overwrite any file on the target server with a trained model file, although the content of the overwrite is not controllable by the attacker.
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
- Path traversal. Limit the folders it can reach at the operating-system level, such as a container or a user with access to only those folders, and keep credentials and keys outside them.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| h2o | PyPI | >= 3.32.1.1, <= 3.46.0 | No fix yet |
- CriticalMCP Path Traversal Allows Full-Filesystem Read and JWT Secret Exfiltration Leading to Account Takeoverlangflow, langflow-base
- Critical@zereight/mcp-gitlab: Unauthenticated arbitrary file read via `upload_markdown` enables PAT exfiltration and full account takeover@zereight/mcp-gitlab
- CriticalFlowise RCE via SQL Database Chain Nodeflowise, flowise-components
- CriticalLangroid: SQLChatAgent dangerous-function blocklist can be bypassed with quoted or schema-qualified pg_read_file callslangroid
- Criticalfast-mcp-telegram: Bearer token path traversal bypasses reserved Telegram session protectionfast-mcp-telegram
- CriticalMCP Toolbox HTTP tool path parameters allow traversal to unintended endpointsgithub.com/googleapis/mcp-toolbox
- 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 Denial of Service (DoS) via `HEAD` Requesth2o
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.