GHSA-m37h-8r48-2cxj CVE-2024-6863 PYSEC-2026-1442
H2O Vulnerable to Execution of Arbitrary Files
- Severity
- 6.5 / 10
- Medium · CVSS 3.0
- Exploit chance (EPSS)
- 0.36%
- Chance of exploitation in the next 30 days. Higher than 29.43% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-749 Exposed Dangerous Method or Function
- Fix
- None yet
- No fixed version published
Description
In h2oai/h2o-3 version 3.46.0, an endpoint exposing a custom EncryptionTool allows an attacker to encrypt any files on the target server with a key of their choosing. The chosen key can also be overwritten, resulting in ransomware-like behavior. This vulnerability makes it possible for an attacker to encrypt arbitrary files with keys of their choice, making it exceedingly difficult for the target to recover the keys needed for decryption.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| ai.h2o:h2o-core | >= 3.32.1.2, <= 3.46.0 |
No fix yet |
PyPI
| Package | Vulnerable | Fixed in |
|---|---|---|
| h2o | >= 3.32.1.2, <= 3.46.0 |
No fix yet |
How to fix
No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.
Severity breakdown
CVSS 3.0 6.5
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
Weakness
CWE-749: Exposed Dangerous Method or Function
The product provides an Applications Programming Interface (API) or similar interface for interaction with external actors, but the interface includes a dangerous method or function that is not properly restricted.
How to prevent it
- Architecture and Design: If you must expose a method, make sure to perform input validation on all arguments, limit access to authorized parties, and protect against all possible vulnerabilities.
- Architecture and Design, Implementation: Identify all exposed functionality. Explicitly list all functionality that must be exposed to some user or set of users. Identify which functionality may be: accessible to all users restricted to a small set of privileged users prevented from being directly accessible at all Ensure that the implemented code follows these expectations. This includes setting the appropriate access modifiers where applicable (public, private, protected, etc.) or not marking ActiveX controls safe-for-scripting.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-qmcv-hh7c-3m56 H2O-3 is Vulnerable to Code Injection | Critical | Also affects ai.h2o:h2o-core |
| GHSA-wj3h-wx8g-x699 H2O has an External Control of File Name or Path vulnerability | Critical | Also affects ai.h2o:h2o-core |
| GHSA-5w3j-gwgh-4rfv H2O affected by a deserialization vulnerability | Critical | Also affects ai.h2o:h2o-core |
| GHSA-g48v-3p35-88jr H2O Vulnerable to Arbitrary File Overwrite | High | Also affects ai.h2o:h2o-core |
| GHSA-5c8j-g96x-cj78 H2O Vulnerable to Denial of Service (DoS) via `HEAD` Request | High | Also affects ai.h2o:h2o-core |
| GHSA-p2vc-m5fv-9w9m H2O Vulnerable to Denial of Service (DoS) via `/3/ImportFiles` Endpoint | High | Also affects ai.h2o:h2o-core |
| GHSA-6w62-3jvj-mfj6 H2O Vulnerable to Denial of Service (DoS) via Large GZIP Parsing | High | Also affects ai.h2o:h2o-core |
| GHSA-47f6-5p7h-5f3h H2O Vulnerable to Arbitrary File Overwrite via File Export | High | Also affects ai.h2o:h2o-core |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor