WaratekVRT Sign in

H2database CVEs with a working exploit

3 CVEs, 1 protected by Waratek

Reset
More filters (1)
Columns
Vendor h2database✕
Overview 3 matches · 1 protected · 0 exploited · 0 CISA KEV · 1 EPSS ≥ 0.5
3matches 1protected33.3% 0exploited0.0% 0CISA KEV0.0% 1EPSS ≥ 0.533.3%
Protected by Waratek 1 33.3% Rule in development 0 0.0% Mitigation candidate 2 66.7% No exploit published 0 0.0%
Critical 1 33.3% High 1 33.3% Medium 1 33.3% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 1 33.3% partly blocked 0 0.0% not blocked 2 66.7% not established 0 0.0% unrecorded 0 0.0%
Exploited 0 0.0% Working exploit published 3 100.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 0 0.0%
split by peak 1 / quarter
Q3 18Q1 19Q3 19Q1 20Q3 20Q1 21Q3 21Q1 22
3 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
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-2018-14335 Medium 2018-07-24 Mitigation candidate Working exploit published An issue was discovered in H2 1.4.197. Insecure handling of permissions in the backup function allows attackers to read sensitive files (outside of their permissions) via a symlink to a fake database file.
CVE-2018-10054 High 2018-04-11 Mitigation candidate Working exploit published H2 1.4.197, as used in Datomic before 0.9.5697 and other products, allows remote code execution because CREATE ALIAS can execute arbitrary Java code. NOTE: the vendor's position is "h2 is not designed to be run outside of a secure environment."