# CVE-2024-8862: h2oai h2o-3 JDBC Connection 1 getConnectionSafe deserialization

> Remote attackers can achieve code execution via unsafe deserialization in the h2o-3 JDBC connection handler, requiring immediate mitigation as no vendor fix is available.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2024
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-fg5m-m723-7mv6, PYSEC-2026-1321

## What is CVE-2024-8862?

CVE-2024-8862 is a medium-severity unsafe deserialization vulnerability in h2oai h2o-3, published on 14 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, has been found in h2oai h2o-3 3.46.0.4. This issue affects the function getConnectionSafe of the file /dtale/chart-data/1 of the component JDBC Connection Handler. The manipulation of the argument query leads to deserialization. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2024-8862?

3 open source packages ship an affected version, including dtale. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dtale` | PyPI | All versions | 3.14.1 |
| `dtale` | PyPI | All versions | 3.14.1 |
| `dtale` | PyPI | All versions | 3.14.1 |

Products: H2o H2o.

## How do I fix CVE-2024-8862?

Upgrade dtale to 3.14.1 or later.

## Is CVE-2024-8862 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8862 exists.

## Other vulnerabilities in h2oai h2o-3

- [CVE-2023-6016](https://insights.sbomify.com/CVE-2023-6016/): H2O Remote Code Execution via POJO Model Import (critical 10.0)
- [CVE-2025-6544](https://insights.sbomify.com/CVE-2025-6544/): Deserialization Vulnerability in h2oai/h2o-3 (critical 9.8)
- [CVE-2024-10553](https://insights.sbomify.com/CVE-2024-10553/): Jdbc Deserialization in h2oai/h2o-3 (critical 9.8)
- [CVE-2023-6569](https://insights.sbomify.com/CVE-2023-6569/): External Control of File Name or Path in h2oai/h2o-3 (critical 9.3)
- [CVE-2023-6013](https://insights.sbomify.com/CVE-2023-6013/): H2O Local File Include (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8862 and fix it if it is affected.

What it is: CVE-2024-8862 is a medium-severity unsafe deserialization vulnerability in h2oai h2o-3, published on 14 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8862 exists.

Affected packages and fixed versions:
- dtale (PyPI): affected all versions; fixed in 3.14.1
- dtale (PyPI): affected all versions; fixed in 3.14.1
- dtale (PyPI): affected all versions; fixed in 3.14.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-8862/ (Markdown: https://insights.sbomify.com/CVE-2024-8862/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-8862
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-8862
- OSV: https://osv.dev/vulnerability/CVE-2024-8862

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-8862/
Summaries are generated and may contain mistakes; the official description above is the record.