DSA-5076: -1 h2database -- security update
h2database - security update
Other sources
Security researchers of JFrog Security and Ismail Aydemir discovered two remote code execution vulnerabilities in the H2 Java SQL database engine which can be exploited through various attack vectors, most notably through the H2 Console and by loading custom classes from remote servers through JNDI. The H2 console is a developer tool and not required by any reverse-dependency in Debian. It has been disabled in (old)stable releases. Database developers are advised to use at least version 2.1.210-1, currently available in Debian unstable.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
h2databaseto a version that resolves this vulnerability.Fixed in 2.1.210-1
Event History
Frequently Asked Questions
Which deployments are most exposed to these vulnerabilities?
Deployments that expose or use the H2 Console are a primary concern, as it is identified as the most notable attack vector. Systems that load custom classes from remote servers through JNDI are also exposed.
Is the H2 Console enabled by default in supported Debian stable releases?
No. The advisory states that the H2 Console has been disabled in Debian stable and oldstable releases, and that no reverse-dependency requires it.
What version should database developers use?
Database developers are advised to use at least version 2.1.210-1, which was available in Debian unstable at the time of the advisory.