h2 is vulnerable to remote code execution. The vulnerability exists due to the use of javax.naming.Context.lookup method
which performs JNDI lookup,as a dangerous function/sink, allowing an attacker to load custom class/ remote LDAP/RMI queries and execute malicious code in a process with H2 Console exposed to the LAN or WAN. (Note: H2 Console connection isnt always used with the H2 database and listens only localhost by default.)
github.com/h2database/h2database/security/advisories/GHSA-h376-j262-vhq6
jfrog.com/blog/the-jndi-strikes-back-unauthenticated-rce-in-h2-database-console/
lists.debian.org/debian-lts-announce/2022/02/msg00017.html
security.netapp.com/advisory/ntap-20220119-0001/
www.debian.org/security/2022/dsa-5076
www.oracle.com/security-alerts/cpuapr2022.html
www.secpod.com/blog/log4shell-critical-remote-code-execution-vulnerability-in-h2database-console/