Deserialization in H2database H2

CVE-2021-42392

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.

Vulnerability class: Insecure Deserialization

Published · last modified .

CVSS v3 metric

CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

EPSS exploit prediction

EPSS: 0.832 (99.7th percentile), scored .

High probability of exploitation in the next 30 days — patch promptly. 100th percentile — 99.7% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2021-42392: held from 0.832 to 0.832.

EPSS over last 30 days · oldest: 0.832 · newest: 0.832 · change: 0.000

Affected products

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2021-42392?
CVE-2021-42392 is a critical-severity vulnerability in H2database H2, classified under Deserialization of Untrusted Data. CVSS score: 9.8/10. Published 2022-01-10.
How severe is CVE-2021-42392?
Critical severity. CVSS v3 base score is 9.8 out of 10.
Is CVE-2021-42392 known to be exploited?
40 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.