Skip to content

← Public intelligence

Maven package

com.h2database:h2

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

4 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.8MavenPublished

    Password exposure in H2 Database

    CVE-2022-45868 · GHSA-22wj-vf5f-wrvj

    Affected
    • Maven com.h2database:h2 >= 1.4.198, < 2.2.220
    Fixed in
    2.2.220· Vendor fix available
    Issue
    The web-based admin console in H2 Database Engine through 2.1.214 can be started via the CLI with the argument -webAdminPassword, which allows the user to specify the password in cleartext for the web admin console. Consequently, a local user (or an attacker that has obtained local access through some means) would be able to discover the password by listing processes and their arguments. NOTE: the vendor states "This is not a vulnerability of H2 Console ... Passwords should never be passed on the command line and every qualified DBA or system administrator is expected to know that."

    Recommended action: Upgrade to 2.2.220 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Critical, CVSS 9.8MavenPublished

    Arbitrary code execution in H2 Console

    CVE-2022-23221 · GHSA-45hx-wfhj-473x

    Affected
    • Maven com.h2database:h2 < 2.1.210
    Fixed in
    2.1.210· Vendor fix available
    Issue
    H2 Console before 2.1.210 allows remote attackers to execute arbitrary code via a jdbc:h2:mem JDBC URL containing the IGNOREUNKNOWNSETTINGS=TRUE;FORBIDCREATION=FALSE;INIT=RUNSCRIPT substring, a different vulnerability than CVE-2021-42392.

    Recommended action: Upgrade to 2.1.210 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Critical, CVSS 9.8MavenPublished

    RCE in H2 Console

    CVE-2021-42392 · GHSA-h376-j262-vhq6

    Affected
    • Maven com.h2database:h2 >= 1.1.100, < 2.0.206
    Fixed in
    2.0.206· Vendor fix available
    Issue
    Impact H2 Console in versions since 1.1.100 (2008-10-14) to 2.0.204 (2021-12-21) inclusive allows loading of custom classes from remote servers through JNDI. H2 Console doesn't accept remote connections by default. If remote access was enabled explicitly and some protection method (such as security constraint) wasn't set, an intruder can load own custom class and execute its code in a process with H2 Console (H2 Server process or a web server with H2 Console servlet). It is also possible to load them by creation a linked table in these versions, but it requires ADMIN privileges and user with ADMIN privileges has full access to the Java process by design. These privileges should never be granted to untrusted users. Patches Since version 2.0.206 H2 Console and linked tables explicitly forbid attempts to specify LDAP URLs for JNDI. Only local data sources can be used. Workarounds H2 Console should never be available to untrusted users. -webAllowOthers is a dangerous setting that should…

    Recommended action: Upgrade to 2.0.206 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  4. High, CVSS 8.1MavenPublished

    Improper Restriction of XML External Entity Reference in com.h2database:h2.

    CVE-2021-23463 · GHSA-7rpj-hg47-cx62

    Affected
    • Maven com.h2database:h2 >= 1.4.198, < 2.0.202
    Fixed in
    2.0.202· Vendor fix available
    Issue
    H2 is an embeddable RDBMS written in Java. The package com.h2database:h2 from 1.4.198 and before 2.0.202 are vulnerable to XML External Entity (XXE) Injection via the org.h2.jdbc.JdbcSQLXML class object, when it receives parsed string data from org.h2.jdbc.JdbcResultSet.getSQLXML() method. If it executes the getSource() method when the parameter is DOMSource.class it will trigger the vulnerability.

    Recommended action: Upgrade to 2.0.202 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →