Overview 8 matches · 3 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
3
37.5%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
5
62.5%
blocked by ARMR today
3
37.5%
partly blocked
0
0.0%
not blocked
5
62.5%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
1
12.5%
Forecast only
0
0.0%
No public exploit
7
87.5%
split by
peak 4 / month
Jun 223
No exploit published3
Medium3
not blocked3
No public exploit3
Jul 224
Protected by Waratek2
No exploit published2
Critical2
High1
Medium1
blocked by ARMR today2
not blocked2
No public exploit4
Aug 220
Sep 220
Oct 221
Protected by Waratek1
Critical1
blocked by ARMR today1
Proof of concept only1
Jun 22Jul 22Aug 22Sep 22Oct 22
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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-34114 | High | 2022-07-22 | Protected by Waratek | No public exploit | Dataease v1.11.1 was discovered to contain a SQL injection 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. |
| CVE-2022-34112 | Medium | 2022-07-22 | No exploit published | No public exploit | An access control issue in the component /api/plugin/uninstall Dataease v1.11.1 allows attackers to arbitrarily uninstall the plugin, a right normally reserved for the administrator. |
| CVE-2022-34781 | Medium | 2022-06-30 | No exploit published | No public exploit | Missing permission checks in Jenkins XebiaLabs XL Release Plugin 22.0.0 and earlier allow attackers with Overall/Read permission to connect to an attacker-specified HTTP server using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins. |
| CVE-2022-34780 | Medium | 2022-06-30 | No exploit published | No public exploit | A cross-site request forgery (CSRF) vulnerability in Jenkins XebiaLabs XL Release Plugin 22.0.0 and earlier allows attackers to connect to an attacker-specified HTTP server using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins. |
| CVE-2022-34779 | Medium | 2022-06-30 | No exploit published | No public exploit | A missing permission check in Jenkins XebiaLabs XL Release Plugin 22.0.0 and earlier allows attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins. |