# CVE-2021-42392: RCE in H2 Console

> Attackers can achieve remote code execution via JNDI injection in the H2 database console, requiring immediate patching.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jan 2022
- **Updated:** 4 Aug 2024
- **Also known as:** CLSA-2026-1787636864, DEBIAN-CVE-2021-42392, GHSA-h376-j262-vhq6, UBUNTU-CVE-2021-42392

## What is CVE-2021-42392?

CVE-2021-42392 is a critical unsafe deserialization vulnerability in Debian Debian Linux, published on 7 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The org.h2.util.JdbcUtils.getConnection method of the H2 database takes as parameters the class name of the driver and URL of the database. An attacker may pass a JNDI driver name and a URL leading to a LDAP or RMI servers, causing remote code execution. This can be exploited through various attack vectors, most notably through the H2 Console which leads to unauthenticated remote code execution.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2021-42392?

2 open source packages ship an affected version, including com.h2database:h2. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.h2database:h2` | Maven | From 1.1.100 | 2.0.206 |
| `com.h2database:h2` | Maven | From 1.1.100 | 2.0.206 |

Products: Debian Debian Linux, H2database H2, Oracle Communications Cloud Native Core Policy.

## How do I fix CVE-2021-42392?

Upgrade com.h2database:h2 to 2.0.206 or later.

## Is CVE-2021-42392 being exploited?

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

Public exploit code:

- https://github.com/cybersecurityworks553/CVE-2021-42392-Detect (github_poc): https://github.com/cybersecurityworks553/CVE-2021-42392-Detect
- https://github.com/Be-Innova/CVE-2021-42392-exploit-lab (github_poc): https://github.com/Be-Innova/CVE-2021-42392-exploit-lab
- H2 Database Console - JNDI Injection RCE (nuclei): http/cves/2021/CVE-2021-42392.yaml

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-42392 and fix it if it is affected.

What it is: CVE-2021-42392 is a critical unsafe deserialization vulnerability in Debian Debian Linux, published on 7 Jan 2022. 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-2021-42392 exists.

Affected packages and fixed versions:
- com.h2database:h2 (Maven): affected from 1.1.100; fixed in 2.0.206
- com.h2database:h2 (Maven): affected from 1.1.100; fixed in 2.0.206

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-2021-42392/ (Markdown: https://insights.sbomify.com/CVE-2021-42392/index.md)
```

## Sources

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

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