CVE-2024-45758

Exp

H2O.ai H2O through 3.46.0.4 allows attackers to arbitrarily set the JDBC URL, leading to deserialization attacks, file reads, and command execution. Exploitation can occur when an attacker has access to post to the ImportSQLTable URI with a JSON document containing a connection_url property with any typical JDBC Connection URL attack payload such as one that uses queryInterceptors.

Published: 2024-09-06 Last update: 2025-09-29 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-45758 is rated Exploit Available (59.5/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.08%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2024-45758

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2024-45758

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 0.21% 0.08% -0.13%
2 2025-11-18 0.07% 0.21% +0.14%
3 2025-03-17 — 0.07% —

Full EPSS history (4 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-45758

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.1 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 5.2 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-45758

GitHub Security Advisory for CVE-2024-45758

GHSA-hrmc-jmp7-mpm2 · Severity: critical · Ecosystem: maven — H2O.ai H2O vulnerable to deserialization attacks via a JDBC Connection URL

OS Trackers for CVE-2024-45758

vendor priority summary link
alpine — CVE-2024-45758: 1 source package rows (h2o); 2 state rows across 1 repos (edge-community); fixed 0, open 2. https://security.alpinelinux.org/vuln/CVE-2024-45758

Affected software / configurations for CVE-2024-45758

Vendor Product Version Raw CPE
h2o h2o <= 3.46.0.4 cpe:2.3:a:h2o:h2o:*:*:*:*:*:*:*:*

References for CVE-2024-45758

cvelogic Threat Intelligence