Security Digest · Vulnerability record

CVE-2024-45758: H2O.ai H2O vulnerable to deserialization attacks via a JDBC Connection URL

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.

CVSS 9.1 Critical EPSS 0.9% · p59

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
  • EPSS 0.9%, percentile 59: FIRST’s model estimates a 0.9% chance of exploitation activity in the next 30 days, higher than 59% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes ai.h2o:h2o-core (Maven) <= 3.46.0.7, no fixed version listed; h2o (PyPI) <= 3.46.0.7, no fixed version listed. Check your lockfile, including transitive dependencies.

What it is

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 connectionurl property with any typical JDBC Connection URL attack payload such as one that uses queryInterceptors.

From the GitHub advisory

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 connectionurl property with any typical JDBC Connection URL attack payload such as one that uses queryInterceptors.

Weakness type: CWE-502.

Product: ai.h2o:h2o-core (Maven) · Assigned by: mitre · Published: 2024-09-06

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
Mavenai.h2o:h2o-core<= 3.46.0.7none listed
PyPIh2o<= 3.46.0.7none listed
VendorProductAffected versions (per CVE record)
n/an/asee vendor advisory

Severity scores

Scored byCVSSScoreVector
CISA-ADP3.19.1 CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub3.19.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Privileges required: none (no login)
  • User interaction: none
  • Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation poc, automatable yes, technical impact total.
  • FIRST EPSS (model of 2026-10-21): 0.91% probability of exploitation activity in the next 30 days; percentile 59.

Timeline

  • — CVE record last updated
  • — CVE record published by mitre
  • — GitHub-reviewed advisory GHSA-hrmc-jmp7-mpm2 published (critical)

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-hrmc-jmp7-mpm2 github.com
  2. CVE.org record CVE-2024-45758 cve.org
  3. NVD entry CVE-2024-45758 nvd.nist.gov

Other references from the CVE record and advisory

  1. spear-shield.notion.site spear-shield.notion.site
  2. gist.github.com gist.github.com
  3. github.com github.com
  4. github.com github.com
  5. github.com github.com
  6. github.com github.com

Critical Maven advisories · Today’s Security Digest