WaratekVRT Sign in
Reset
More filters (1)
Columns
Including CVEs outside Waratek scope✕Product dataease✕
Overview 15 matches · 4 in Waratek scope · 2 protected · 0 exploited · 0 CISA KEV · 2 public PoC · 1 EPSS ≥ 0.5
15matches 4in Waratek scope26.7% 2protected13.3% 0exploited0.0% 0CISA KEV0.0% 2public PoC13.3% 1EPSS ≥ 0.56.7%
Protected by Waratek 2 13.3% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 2 13.3% Outside Waratek scope 0 0.0% Not applicable 11 73.3% Withdrawn CVE 0 0.0%
Critical 15 100.0% High 0 0.0% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 2 13.3% partly blocked 0 0.0% not blocked 13 86.7% not established 0 0.0% unrecorded 0 0.0%
Exploited 0 0.0% Working exploit published 2 13.3% Proof of concept only 8 53.3% Forecast only 0 0.0% No public exploit 5 33.3%
split by peak 3 / quarter
Not applicable: 11No exploit published: 2Protected by Waratek: 2 Critical: 15 not blocked: 13blocked by ARMR today: 2 No public exploit: 5Proof of concept only: 8Working exploit published: 2
Q3 222 Protected by Waratek1 No exploit published1 Critical2 blocked by ARMR today1 not blocked1 No public exploit2 Q4 221 Protected by Waratek1 Critical1 blocked by ARMR today1 Proof of concept only1 Q1 231 Not applicable1 Critical1 not blocked1 Proof of concept only1 Q2 231 Not applicable1 Critical1 not blocked1 No public exploit1 Q3 231 Not applicable1 Critical1 not blocked1 Proof of concept only1 Q4 230 Q1 241 Not applicable1 Critical1 not blocked1 Proof of concept only1 Q2 240 Q3 241 No exploit published1 Critical1 not blocked1 No public exploit1 Q4 243 Not applicable3 Critical3 not blocked3 Working exploit published1 Proof of concept only1 No public exploit1 Q1 252 Not applicable2 Critical2 not blocked2 Working exploit published1 Proof of concept only1 Q2 250 Q3 250 Q4 250 Q1 262 Not applicable2 Critical2 not blocked2 Proof of concept only2
Q3 22Q1 23Q3 23Q1 24Q3 24Q1 25Q3 25Q1 26
15 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-2026-32140 Critical 2026-03-12 Not applicable Proof of concept only Dataease is an open source data visualization analysis tool. Prior to 2.10.20, By controlling the IniFile parameter, an attacker can force the JDBC driver to load an attacker-controlled configuration file. This configuration file can inject dangerous JDBC properties, leading to remote code execution. The Redshift JDBC driver execution flow reaches a method named getJdbcIniFile. The getJdbcIniFile method implements an aggressive automatic configuration file discovery mechanism. If not explicitly restricted, it searches for a file named rsjdbc.ini. In a JDBC URL context, users can explicitly specify the configuration file via URL parameters, which allows arbitrary files on the server to be loaded as JDBC configuration files. Within the Redshift JDBC driver properties, the parameter IniFile is explicitly supported and used to load an external configuration file. This vulnerability is fixed in 2.10.20.
CVE-2026-32137 Critical 2026-03-12 Not applicable Proof of concept only Dataease is an open source data visualization analysis tool. Prior to 2.10.20, The table parameter for /de2api/datasource/previewData is directly concatenated into the SQL statement without any filtering or parameterization. Since tableName is a user-controllable string, attackers can inject malicious SQL statements by constructing malicious table names. This vulnerability is fixed in 2.10.20.
CVE-2024-57707 Critical 2025-02-07 Not applicable Proof of concept only An issue in DataEase v1 allows an attacker to execute arbitrary code via the user account and password components.
CVE-2024-56511 Critical 2025-01-10 Not applicable Working exploit published DataEase is an open source data visualization analysis tool. Prior to 2.10.4, there is a flaw in the authentication in the io.dataease.auth.filter.TokenFilter class, which can be bypassed and cause the risk of unauthorized access. In the io.dataease.auth.filter.TokenFilter class, ”request.getRequestURI“ is used to obtain the request URL, and it is passed to the "WhitelistUtils.match" method to determine whether the URL request is an interface that does not require authentication. The "match" method filters semicolons, but this is not enough. When users set "server.servlet.context-path" when deploying products, there is still a risk of being bypassed, which can be bypassed by any whitelist prefix /geo/../context-path/. The vulnerability has been fixed in v2.10.4.
CVE-2024-52295 Critical 2024-11-13 Not applicable Proof of concept only DataEase is an open source data visualization analysis tool. Prior to 2.10.2, DataEase allows attackers to forge jwt and take over services. The JWT secret is hardcoded in the code, and the UID and OID are hardcoded. The vulnerability has been fixed in v2.10.2.
CVE-2024-47073 Critical 2024-11-07 Not applicable Working exploit published DataEase is an open source data visualization analysis tool that helps users quickly analyze data and gain insights into business trends. In affected versions a the lack of signature verification of jwt tokens allows attackers to forge jwts which then allow access to any interface. The vulnerability has been fixed in v2.10.2 and all users are advised to upgrade. There are no known workarounds for this vulnerability.
CVE-2024-47074 Critical 2024-10-11 Not applicable No public exploit DataEase is an open source data visualization analysis tool. In Dataease, the PostgreSQL data source in the data source function can customize the JDBC connection parameters and the PG server target to be connected. In backend/src/main/java/io/dataease/provider/datasource/JdbcProvider.java, PgConfiguration class don't filter any parameters, directly concat user input. So, if the attacker adds some parameters in JDBC url, and connect to evil PG server, the attacker can trigger the PG jdbc deserialization vulnerability, and eventually the attacker can execute through the deserialization vulnerability system commands and obtain server privileges. The vulnerability has been fixed in v1.18.25.
CVE-2024-46997 Critical 2024-09-23 No exploit published No public exploit DataEase is an open source data visualization analysis tool. Prior to version 2.10.1, an attacker can achieve remote command execution by adding a carefully constructed h2 data source connection string. The vulnerability has been fixed in v2.10.1.
CVE-2024-23328 Critical 2024-02-29 Not applicable Proof of concept only Dataease is an open source data visualization analysis tool. A deserialization vulnerability exists in the DataEase datasource, which can be exploited to execute arbitrary code. The location of the vulnerability code is `core/core-backend/src/main/java/io/dataease/datasource/type/Mysql.java.` The blacklist of mysql jdbc attacks can be bypassed and attackers can further exploit it for deserialized execution or reading arbitrary files. This vulnerability is patched in 1.18.15 and 2.3.0.
CVE-2023-37258 Critical 2023-07-25 Not applicable Proof of concept only DataEase is an open source data visualization analysis tool. Prior to version 1.18.9, DataEase has a SQL injection vulnerability that can bypass blacklists. The vulnerability has been fixed in v1.18.9. There are no known workarounds.
CVE-2023-33963 Critical 2023-06-01 Not applicable No public exploit DataEase is an open source data visualization and analysis tool. Prior to version 1.18.7, a deserialization vulnerability exists in the DataEase datasource, which can be exploited to execute arbitrary code. The vulnerability has been fixed in v1.18.7. There are no known workarounds aside from upgrading.
CVE-2023-28437 Critical 2023-03-25 Not applicable Proof of concept only Dataease is an open source data visualization and analysis tool. The blacklist for SQL injection protection is missing entries. This vulnerability has been fixed in version 1.18.5. There are no known workarounds.
CVE-2022-39312 Critical 2022-10-25 Protected by Waratek Proof of concept only Dataease is an open source data visualization analysis tool. Dataease prior to 1.15.2 has a deserialization vulnerability. In Dataease, the Mysql data source in the data source function can customize the JDBC connection parameters and the Mysql server target to be connected. In `backend/src/main/java/io/dataease/provider/datasource/JdbcProvider.java`, the `MysqlConfiguration` class does not filter any parameters. If an attacker adds some parameters to a JDBC url and connects to a malicious mysql server, the attacker can trigger the mysql jdbc deserialization vulnerability. Through the deserialization vulnerability, the attacker can execute system commands and obtain server privileges. Version 1.15.2 contains a patch for this issue.
CVE-2022-34115 Critical 2022-07-22 Protected by Waratek No public exploit DataEase v1.11.1 was discovered to contain a arbitrary file write vulnerability via the parameter dataSourceId.
CVE-2022-34113 Critical 2022-07-22 No exploit published No public exploit An issue in the component /api/plugin/upload of Dataease v1.11.1 allows attackers to execute arbitrary code via a crafted plugin.