← Back
CVE-2024-7768
Vulnerability in h2o (CVE-2024-7768)
Summary
vulnerability in h2o (CVE-2024-7768). Risk of unauthorized operations or information disclosure. Exploitable via ``path``.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-7768** has been found in h2o.
Attackers can target a specific entry point like ``path`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "h2o CVE-2024-7768" on the vendor's site.
CVE-2024-7768 (h2o) — CWE-400 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `path`
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-400) exists in h2o. Attackers reach the vulnerable code path via ``path`` without authentication.
📍 Affected scope
h2o — . Attack surface: `path`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'h2o' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'h2o' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `h2o` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
h2o
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"3.46.1"}]}]
Maven
ai.h2o:h2o-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"3.46.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-7768
- advisory https://github.com/advisories/GHSA-p2vc-m5fv-9w9m
- package https://github.com/h2oai/h2o-3
- package https://pypi.org/project/h2o
- web https://github.com/h2oai/h2o-3/blob/7d418fa19d3ab434f742818e37f891bef9102c97/h2o-core/src/main/java/water/api/ImportFilesHandler.java#L19
- web https://huntr.com/bounties/3fe640df-bef4-4072-8890-0d12bc2818f6