CVE-2024-5986
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability in h2oai/h2o-3 version 3.46.0.1 allows remote attackers to write arbitrary data to any file on the server. This is achieved by exploiting the `/3/Parse` endpoint to inject attacker-controlled data as the header of an empty file, which is then exported using the `/3/Frames/framename/export` endpoint. The impact of this vulnerability includes the potential for remote code execution and complete access to the system running h2o-3, as attackers can overwrite critical files such as private SSH keys or script files.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA path traversal/file injection vulnerability in h2oai/h2o-3 v3.46.0.1 allows remote attackers to write arbitrary data to any file on the server by injecting attacker-controlled content as a file header via the /3/Parse endpoint, then exporting it to an arbitrary location using /3/Frames/framename/export. This enables overwriting critical system files for potential remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed h2o-3 versionRun 'h2o --version' or check the H2O jar file name/version metadata in your deploymentAffected if The version is 3.46.0.1 exactly, or falls within the 3.46.x branch prior to patching
-
Verify network exposure of the /3/Parse endpointReview your firewall rules, reverse proxy configuration, or security group settings to determine if port/service hosting /3/Parse is reachable from untrusted networksAffected if The /3/Parse endpoint is exposed to the internet or untrusted external networks
-
Verify network exposure of the /3/Frames/*/export endpointReview network access controls to determine if the /3/Frames/*/export endpoint is reachable from untrusted networksAffected if The /3/Frames/*/export endpoint is exposed to the internet or untrusted external networks
-
Review H2O server logs for suspicious parse and export operationsExamine H2O logs (stdout, file logs, or logging backend) for entries involving /3/Parse and /3/Frames/*/export with unexpected file paths or destinationsAffected if Logs show export operations to paths outside the intended H2O data directory or to system directories such as /etc, /usr, or /opt
-
Inspect the H2O data directory for unexpected filesList files in the configured H2O frame storage directory and check for recently created files in system directories or config paths that should not be writable by the H2O serviceAffected if Unexpected files appear in sensitive system directories or configuration files have been modified outside of normal H2O operation
You are affected if h2o-3 version 3.46.0.1 is running AND either the /3/Parse or /3/Frames/*/export endpoints are network-accessible to untrusted users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade h2o-3 to a patched version; if immediate upgrade is not feasible, restrict network access to the /3/Parse and /3/Frames/*/export endpoints and implement strict file write validation.
- Consultation6.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5986 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-5986 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data