Overview 11 matches · 5 in Waratek scope · 3 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
11matches
5in Waratek scope45.5%
3protected27.3%
0exploited0.0%
0CISA KEV0.0%
0public PoC0.0%
0EPSS ≥ 0.50.0%
Protected by Waratek
3
27.3%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
2
18.2%
Outside Waratek scope
0
0.0%
Not applicable
6
54.5%
Withdrawn CVE
0
0.0%
blocked by ARMR today
3
27.3%
partly blocked
0
0.0%
not blocked
8
72.7%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
4
36.4%
Forecast only
0
0.0%
No public exploit
7
63.6%
split by
peak 2 / year
20171
Not applicable1
Critical1
not blocked1
No public exploit1
20181
Not applicable1
Critical1
not blocked1
No public exploit1
20190
20200
20211
Not applicable1
Critical1
not blocked1
No public exploit1
20221
Not applicable1
Critical1
not blocked1
No public exploit1
20232
Not applicable2
Critical2
not blocked2
No public exploit2
20241
Protected by Waratek1
Critical1
blocked by ARMR today1
Proof of concept only1
20252
Protected by Waratek2
Critical2
blocked by ARMR today2
Proof of concept only2
20262
No exploit published2
Critical2
not blocked2
Proof of concept only1
No public exploit1
2017201820192020202120222023202420252026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2026-3960 | Critical | 2026-04-23 | No exploit published | Proof of concept only | A critical remote code execution vulnerability exists in the unauthenticated REST API endpoint /99/ImportSQLTable in H2O-3 version 3.46.0.9 and prior. The vulnerability arises due to insufficient security controls in the parameter blacklist mechanism, which only targets MySQL JDBC driver-specific dangerous parameters. An attacker can bypass these controls by switching the JDBC URL protocol to jdbc:postgresql: and exploiting PostgreSQL JDBC driver-specific parameters such as socketFactory and socketFactoryArg. This allows unauthenticated attackers to execute arbitrary code on the H2O-3 server with the privileges of the H2O-3 process. The issue is resolved in version 3.46.0.10. |
| CVE-2024-5986 | Critical | 2026-02-02 | No exploit published | No public exploit | A vulnerability in h2oai/h2o-3 version 3.46.0.1 allows remote attackers to write arbitrary data to any file on the server. This is achieved by exploiting the `/3/Parse` endpoint to inject attacker-controlled data as the header of an empty file, which is then exported using the `/3/Frames/framename/export` endpoint. The impact of this vulnerability includes the potential for remote code execution and complete access to the system running h2o-3, as attackers can overwrite critical files such as private SSH keys or script files. |
| CVE-2025-6544 | Critical | 2025-09-21 | Protected by Waratek | Proof of concept only | A deserialization vulnerability exists in h2oai/h2o-3 versions <= 3.46.0.8, allowing attackers to read arbitrary system files and execute arbitrary code. The vulnerability arises from improper handling of JDBC connection parameters, which can be exploited by bypassing regular expression checks and using double URL encoding. This issue impacts all users of the affected versions. |
| CVE-2024-10553 | Critical | 2025-03-20 | Protected by Waratek | Proof of concept only | A vulnerability in the h2oai/h2o-3 REST API versions 3.46.0.4 allows unauthenticated remote attackers to execute arbitrary code via deserialization of untrusted data. The vulnerability exists in the endpoints POST /99/ImportSQLTable and POST /3/SaveToHiveTable, where user-controlled JDBC URLs are passed to DriverManager.getConnection, leading to deserialization if a MySQL or PostgreSQL driver is available in the classpath. This issue is fixed in version 3.47.0. |
| CVE-2024-45758 | Critical | 2024-09-06 | Protected by Waratek | Proof of concept only | H2O.ai H2O through 3.46.0.4 allows attackers to arbitrarily set the JDBC URL, leading to deserialization attacks, file reads, and command execution. Exploitation can occur when an attacker has access to post to the ImportSQLTable URI with a JSON document containing a connection_url property with any typical JDBC Connection URL attack payload such as one that uses queryInterceptors. |
| CVE-2023-6016 | Critical | 2023-11-16 | Not applicable | No public exploit | An attacker is able to gain remote code execution on a server hosting the H2O dashboard through it's POJO model import feature. |
| CVE-2023-39281 | Critical | 2023-11-01 | Not applicable | No public exploit | A stack buffer overflow vulnerability discovered in AsfSecureBootDxe in Insyde InsydeH2O with kernel 5.0 through 5.5 allows attackers to run arbitrary code execution during the DXE phase. |
| CVE-2021-41842 | Critical | 2022-01-06 | Not applicable | No public exploit | An issue was discovered in AtaLegacySmm in the kernel 5.0 before 05.08.46, 5.1 before 05.16.46, 5.2 before 05.26.46, 5.3 before 05.35.46, 5.4 before 05.43.46, and 5.5 before 05.51.45 in Insyde InsydeH2O. Code execution can occur because the SMI handler lacks a CommBuffer check. |
| CVE-2020-5955 | Critical | 2021-11-03 | Not applicable | No public exploit | An issue was discovered in Int15MicrocodeSmm in Insyde InsydeH2O before 2021-10-14 on Intel client chipsets. A caller may be able to escalate privileges. |
| CVE-2018-0608 | Critical | 2018-06-26 | Not applicable | No public exploit | Buffer overflow in H2O version 2.2.4 and earlier allows remote attackers to execute arbitrary code or cause a denial of service (DoS) via unspecified vectors. |
| CVE-2016-7835 | Critical | 2017-06-09 | Not applicable | No public exploit | Use-after-free vulnerability in H2O allows remote attackers to cause a denial-of-service (DoS) or obtain server certificate private keys and possibly other information. |