CVE-2024-8062
H2O 3.46.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2024-8062 is a high-severity Synchronous Access of Remote Resource without Timeout (CWE-1088) vulnerability in H2O H2O. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
This vulnerability is AI-related — categorised as Machine Learning Libraries; in the Other ATLAS/OWASP Terms risk domain.
The strongest mitigations our analysis identified map to SC-10 (Network Disconnect) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-8062 is a denial-of-service vulnerability in the typeahead endpoint of h2oai/h2o-3 version 3.46.0. The endpoint performs a HEAD request to verify the existence of a specified resource without setting a timeout, allowing resource exhaustion when the request hangs.
The vulnerability can be exploited remotely by unauthenticated attackers with low complexity, as indicated by its CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H). An attacker sends multiple requests specifying an attacker-controlled server that hangs on the HEAD request, causing the application to block and become unresponsive to other requests. This leads to a denial of service with high availability impact, mapped to CWE-1088.
Mitigation details are available in the advisory published on Huntr.dev at https://huntr.com/bounties/a04190d9-4acb-449a-9a7f-f1bf6be1ed23. The CVE was published on 2025-03-20.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-6929
Vulnerability Data
A vulnerability in the typeahead endpoint of h2oai/h2o-3 version 3.46.0 allows for a denial of service. The endpoint performs a `HEAD` request to verify the existence of a specified resource without setting a timeout. An attacker can exploit this by…
more
sending multiple requests to an attacker-controlled server that hangs, causing the application to block and become unresponsive to other requests.
- CWE(s)
AI Security AnalysisAI
- AI Category
- Machine Learning Libraries
- Risk Domain
- Other ATLAS/OWASP Terms
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Matched keywords: h2o
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
SC-10 requires terminating network connections after a defined period, directly enforcing timeouts on remote synchronous calls.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect missing timeouts, providing partial coverage of both the weakness and the control.
Redundancy and failover mechanisms can mitigate the impact of a hung synchronous call but do not enforce timeouts.
Network security controls can include connection-timeout policies, yet the weakness is a coding-level omission.
Secure SDLC practices require timeout handling for external calls, directly addressing the missing timeout.
Application security requirements typically mandate timeout settings for remote resource access.
Secure architecture principles encourage defensive coding patterns such as timeouts, but do not prescribe them explicitly.