com.h2database H2 CVEs
4 CVEs, 3 protected by Waratek
Overview 4 matches · 3 protected · 0 exploited · 0 CISA KEV · 1 public PoC · 2 EPSS ≥ 0.5
Protected by Waratek
3
75.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
1
25.0%
blocked by ARMR today
3
75.0%
partly blocked
0
0.0%
not blocked
1
25.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
1
25.0%
Proof of concept only
2
50.0%
Forecast only
0
0.0%
No public exploit
1
25.0%
split by
peak 2 / month
Dec 211
Protected by Waratek1
Critical1
blocked by ARMR today1
No public exploit1
Jan 222
Protected by Waratek2
Critical2
blocked by ARMR today2
Working exploit published1
Proof of concept only1
Feb 220
Mar 220
Apr 220
May 220
Jun 220
Jul 220
Aug 220
Sep 220
Oct 220
Nov 221
No exploit published1
High1
not blocked1
Proof of concept only1
Dec 21Jan 22Feb 22Mar 22Apr 22May 22Jun 22Jul 22Aug 22Sep 22Oct 22Nov 22
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-45868 | High | 2022-11-23 | No exploit published | Proof of concept only | The web-based admin console in H2 Database Engine before 2.2.220 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." Nonetheless, the issue was fixed in 2.2.220. |
| CVE-2022-23221 | Critical | 2022-01-19 | Protected by Waratek | Proof of concept only | H2 Console before 2.1.210 allows remote attackers to execute arbitrary code via a jdbc:h2:mem JDBC URL containing the IGNORE_UNKNOWN_SETTINGS=TRUE;FORBID_CREATION=FALSE;INIT=RUNSCRIPT substring, a different vulnerability than CVE-2021-42392. |
| CVE-2021-42392 | Critical | 2022-01-10 | Protected by Waratek | Working exploit published | 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. |
| CVE-2021-23463 | Critical | 2021-12-10 | Protected by Waratek | No public exploit | 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. |