Overview 105 matches · 52 protected · 26 CISA KEV · 81 public PoC · 42 EPSS ≥ 0.5
Protected by Waratek
53
50.5%
Rule in development
3
2.9%
Mitigation candidate
49
46.7%
No exploit published
0
0.0%
blocked by ARMR today
52
49.5%
partly blocked
1
1.0%
not blocked
47
44.8%
not established
5
4.8%
unrecorded
0
0.0%
Exploited
105
100.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 9 / quarter
Q2 221
Protected by Waratek1
Medium1
blocked by ARMR today1
Exploited1
Q3 224
Protected by Waratek2
Mitigation candidate2
High4
blocked by ARMR today2
not blocked2
Exploited4
Q4 224
Protected by Waratek4
Critical3
High1
blocked by ARMR today4
Exploited4
Q1 235
Protected by Waratek4
Mitigation candidate1
Critical2
High3
blocked by ARMR today4
not blocked1
Exploited5
Q2 236
Protected by Waratek4
Mitigation candidate2
Critical2
High4
blocked by ARMR today4
not blocked1
not established1
Exploited6
Q3 234
Protected by Waratek2
Mitigation candidate2
Critical3
High1
blocked by ARMR today2
not blocked2
Exploited4
Q4 237
Protected by Waratek1
Mitigation candidate6
Critical5
High2
blocked by ARMR today1
not blocked5
not established1
Exploited7
Q1 249
Protected by Waratek2
Mitigation candidate7
Critical4
High4
Medium1
blocked by ARMR today2
not blocked7
Exploited9
Q2 246
Protected by Waratek4
Mitigation candidate2
Critical3
High3
blocked by ARMR today4
not blocked2
Exploited6
Q3 245
Protected by Waratek4
Mitigation candidate1
Critical1
High3
Medium1
blocked by ARMR today3
partly blocked1
not blocked1
Exploited5
Q4 244
Protected by Waratek2
Mitigation candidate2
Critical3
High1
blocked by ARMR today2
not blocked2
Exploited4
Q1 256
Protected by Waratek3
Mitigation candidate3
Critical3
High1
Medium2
blocked by ARMR today3
not blocked3
Exploited6
Q2 258
Protected by Waratek2
Rule in development1
Mitigation candidate5
Critical3
High2
Medium3
blocked by ARMR today2
not blocked6
Exploited8
Q3 258
Protected by Waratek3
Rule in development1
Mitigation candidate4
Critical5
High1
Medium2
blocked by ARMR today3
not blocked5
Exploited8
Q4 259
Protected by Waratek3
Rule in development1
Mitigation candidate5
Critical6
High2
Medium1
blocked by ARMR today3
not blocked4
not established2
Exploited9
Q1 263
Protected by Waratek2
Mitigation candidate1
Critical2
High1
blocked by ARMR today2
not established1
Exploited3
Q2 268
Protected by Waratek6
Mitigation candidate2
Critical3
High5
blocked by ARMR today6
not blocked2
Exploited8
Q3 266
Protected by Waratek2
Mitigation candidate4
Critical5
High1
blocked by ARMR today2
not blocked4
Exploited6
Q4 262
Protected by Waratek2
Critical2
blocked by ARMR today2
Exploited2
Q2 22Q4 22Q2 23Q4 23Q2 24Q4 24Q2 25Q4 25Q2 26Q4 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-36537 | High | 2022-08-26 | Mitigation candidate | Exploited | ZK Framework v9.6.1, 9.6.0.1, 9.5.1.3, 9.0.1.2 and 8.6.4.1 allows attackers to access sensitive information via a crafted POST request sent to the component AuUploader. |
| CVE-2022-31197 | High | 2022-08-03 | Protected by Waratek | Exploited | PostgreSQL JDBC Driver (PgJDBC for short) allows Java programs to connect to a PostgreSQL database using standard, database independent Java code. The PGJDBC implementation of the `java.sql.ResultRow.refreshRow()` method is not performing escaping of column names so a malicious column name that contains a statement terminator, e.g. `;`, could lead to SQL injection. This could lead to executing additional SQL commands as the application's JDBC user. User applications that do not invoke the `ResultSet.refreshRow()` method are not impacted. User application that do invoke that method are impacted if the underlying database that they are querying via their JDBC application may be under the control of an attacker. The attack requires the attacker to trick the user into executing SQL against a table name who's column names would contain the malicious SQL and subsequently invoke the `refreshRow()` method on the ResultSet. Note that the application's JDBC user and the schema owner need not be the same. A JDBC application that executes as a privileged user querying database schemas owned by potentially malicious less-privileged users would be vulnerable. In that situation it may be possible for the malicious user to craft a schema that causes the application to execute commands as the privileged user. Patched versions will be released as `42.2.26` and `42.4.1`. Users are advised to upgrade. There are no known workarounds for this issue. |
| CVE-2022-36883 | High | 2022-07-27 | Mitigation candidate | Exploited | A missing permission check in Jenkins Git Plugin 4.11.3 and earlier allows unauthenticated attackers to trigger builds of jobs configured to use an attacker-specified Git repository and to cause them to check out an attacker-specified commit. |
| CVE-2022-33891 | High | 2022-07-18 | Protected by Waratek | Exploited | The Apache Spark UI offers the possibility to enable ACLs via the configuration option spark.acls.enable. With an authentication filter, this checks whether a user has access permissions to view or modify the application. If ACLs are enabled, a code path in HttpSecurityFilter can allow someone to perform impersonation by providing an arbitrary user name. A malicious user might then be able to reach a permission check function that will ultimately build a Unix shell command based on their input, and execute it. This will result in arbitrary shell command execution as the user Spark is currently running as. This affects Apache Spark versions 3.0.3 and earlier, versions 3.1.1 to 3.1.2, and versions 3.2.0 to 3.2.1. |
| CVE-2022-34305 | Medium | 2022-06-23 | Protected by Waratek | Exploited | In Apache Tomcat 10.1.0-M1 to 10.1.0-M16, 10.0.0-M1 to 10.0.22, 9.0.30 to 9.0.64 and 8.5.50 to 8.5.81 the Form authentication example in the examples web application displayed user provided data without filtering, exposing a XSS vulnerability. |