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.
Remediation
References
https://github.com/h2database/h2database/security/advisories/GHSA-h376-j262-vhq6
https://jfrog.com/blog/the-jndi-strikes-back-unauthenticated-rce-in-h2-database-console/
https://lists.debian.org/debian-lts-announce/2022/02/msg00017.html
https://security.netapp.com/advisory/ntap-20220119-0001/
https://www.debian.org/security/2022/dsa-5076
https://www.oracle.com/security-alerts/cpuapr2022.html
https://www.secpod.com/blog/log4shell-critical-remote-code-execution-vulnerability-in-h2database-console/
Related Vulnerabilities
CVE-2018-3784 Vulnerability in npm package cryo
CVE-2021-29620 Vulnerability in maven package com.epam.reportportal:service-api
CVE-2020-2323 Vulnerability in maven package io.jenkins.plugins:chaos-monkey
CVE-2018-16493 Vulnerability in npm package static-resource-server
CVE-2022-41932 Vulnerability in maven package org.xwiki.platform:xwiki-platform-oldcore