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.
References
Link | Resource |
---|---|
https://github.com/h2database/h2database/security/advisories/GHSA-h376-j262-vhq6 | Mitigation Third Party Advisory |
https://jfrog.com/blog/the-jndi-strikes-back-unauthenticated-rce-in-h2-database-console/ | Exploit Technical Description Vendor Advisory |
https://security.netapp.com/advisory/ntap-20220119-0001/ | Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2022/02/msg00017.html | Mailing List Third Party Advisory |
https://www.debian.org/security/2022/dsa-5076 | Third Party Advisory |
https://www.oracle.com/security-alerts/cpuapr2022.html | Patch Third Party Advisory |
https://www.secpod.com/blog/log4shell-critical-remote-code-execution-vulnerability-in-h2database-console/ |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
|
Information
Published : 2022-01-10 06:10
Updated : 2023-02-24 14:15
NVD link : CVE-2021-42392
Mitre link : CVE-2021-42392
JSON object : View
CWE
CWE-502
Deserialization of Untrusted Data
Products Affected
h2database
- h2
debian
- debian_linux
oracle
- communications_cloud_native_core_policy