Overview 207 matches · 78 protected · 91 exploited · 28 CISA KEV · 73 EPSS ≥ 0.5
Protected by Waratek
79
38.2%
Rule in development
4
1.9%
Mitigation candidate
124
59.9%
No exploit published
0
0.0%
blocked by ARMR today
78
37.7%
partly blocked
1
0.5%
not blocked
128
61.8%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
91
44.0%
Working exploit published
78
37.7%
Proof of concept only
38
18.4%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 20 / quarter
Q1 2211
Protected by Waratek7
Mitigation candidate4
Critical8
High2
Medium1
blocked by ARMR today7
not blocked4
Exploited3
Working exploit published4
Proof of concept only4
Q2 2218
Protected by Waratek10
Rule in development1
Mitigation candidate7
Critical9
High7
Medium2
blocked by ARMR today10
not blocked8
Exploited8
Working exploit published5
Proof of concept only5
Q3 228
Protected by Waratek3
Mitigation candidate5
Critical2
High6
blocked by ARMR today3
not blocked5
Exploited3
Working exploit published1
Proof of concept only4
Q4 226
Protected by Waratek3
Mitigation candidate3
Critical5
Medium1
blocked by ARMR today3
not blocked3
Exploited3
Working exploit published1
Proof of concept only2
Q1 234
Protected by Waratek3
Mitigation candidate1
Critical2
High2
blocked by ARMR today3
not blocked1
Exploited3
Proof of concept only1
Q2 2320
Protected by Waratek6
Mitigation candidate14
Critical9
High5
Medium6
blocked by ARMR today6
not blocked14
Exploited4
Working exploit published15
Proof of concept only1
Q3 239
Protected by Waratek2
Mitigation candidate7
Critical2
High5
Medium2
blocked by ARMR today2
not blocked7
Exploited2
Working exploit published4
Proof of concept only3
Q4 2316
Protected by Waratek3
Mitigation candidate13
Critical6
High6
Medium4
blocked by ARMR today3
not blocked13
Exploited6
Working exploit published8
Proof of concept only2
Q1 2411
Protected by Waratek3
Mitigation candidate8
Critical3
High4
Medium4
blocked by ARMR today3
not blocked8
Exploited5
Working exploit published3
Proof of concept only3
Q2 248
Protected by Waratek4
Mitigation candidate4
Critical4
High4
blocked by ARMR today4
not blocked4
Exploited6
Working exploit published1
Proof of concept only1
Q3 2411
Protected by Waratek4
Mitigation candidate7
Critical3
High6
Medium2
blocked by ARMR today3
partly blocked1
not blocked7
Exploited4
Working exploit published6
Proof of concept only1
Q4 249
Protected by Waratek3
Mitigation candidate6
Critical6
High2
Low1
blocked by ARMR today3
not blocked6
Exploited3
Working exploit published4
Proof of concept only2
Q1 255
Protected by Waratek2
Mitigation candidate3
Critical2
High1
Medium2
blocked by ARMR today2
not blocked3
Exploited4
Working exploit published1
Q2 2513
Protected by Waratek4
Rule in development1
Mitigation candidate8
Critical5
High3
Medium5
blocked by ARMR today4
not blocked9
Exploited8
Working exploit published4
Proof of concept only1
Q3 2510
Protected by Waratek4
Mitigation candidate6
Critical5
High1
Medium4
blocked by ARMR today4
not blocked6
Exploited7
Working exploit published3
Q4 2512
Protected by Waratek5
Rule in development2
Mitigation candidate5
Critical5
High3
Medium4
blocked by ARMR today5
not blocked7
Exploited7
Working exploit published4
Proof of concept only1
Q1 268
Protected by Waratek2
Mitigation candidate6
Critical3
High3
Medium1
Low1
blocked by ARMR today2
not blocked6
Exploited2
Working exploit published2
Proof of concept only4
Q2 2614
Protected by Waratek8
Mitigation candidate6
Critical4
High6
Medium4
blocked by ARMR today8
not blocked6
Exploited7
Working exploit published5
Proof of concept only2
Q3 2613
Protected by Waratek2
Mitigation candidate11
Critical7
High4
Medium2
blocked by ARMR today2
not blocked11
Exploited5
Working exploit published7
Proof of concept only1
Q4 261
Protected by Waratek1
Critical1
blocked by ARMR today1
Exploited1
Q2 22Q4 22Q2 23Q4 23Q2 24Q4 24Q2 25Q4 25Q2 26Q4 26
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2021-44521 | Critical | 2022-02-11 | Protected by Waratek | Working exploit published | When running Apache Cassandra with the following configuration: enable_user_defined_functions: true enable_scripted_user_defined_functions: true enable_user_defined_functions_threads: false it is possible for an attacker to execute arbitrary code on the host. The attacker would need to have enough permissions to create user defined functions in the cluster to be able to exploit this. Note that this configuration is documented as unsafe, and will continue to be considered unsafe after this CVE. |
| CVE-2022-23944 | Critical | 2022-01-25 | Mitigation candidate | Working exploit published | User can access /plugin api without authentication. This issue affected Apache ShenYu 2.4.0 and 2.4.1. |
| CVE-2022-21371 | High | 2022-01-19 | Protected by Waratek | Exploited | Vulnerability in the Oracle WebLogic Server product of Oracle Fusion Middleware (component: Web Container). Supported versions that are affected are 12.1.3.0.0, 12.2.1.3.0, 12.2.1.4.0 and 14.1.1.0.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle WebLogic Server. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle WebLogic Server accessible data. CVSS 3.1 Base Score 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). |
| CVE-2021-35587 | Critical | 2022-01-19 | Protected by Waratek | Exploited | Vulnerability in the Oracle Access Manager product of Oracle Fusion Middleware (component: OpenSSO Agent). Supported versions that are affected are 11.1.2.3.0, 12.2.1.3.0 and 12.2.1.4.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Access Manager. Successful attacks of this vulnerability can result in takeover of Oracle Access Manager. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). |
| CVE-2022-23305 | Critical | 2022-01-18 | Protected by Waratek | Proof of concept only | By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions. |
| CVE-2021-43297 | Critical | 2022-01-10 | Protected by Waratek | Proof of concept only | A deserialization vulnerability existed in dubbo hessian-lite 3.2.11 and its earlier versions, which could lead to malicious code execution. Most Dubbo users use Hessian2 as the default serialization/deserialization protocol, during Hessian catch unexpected exceptions, Hessian will log out some imformation for users, which may cause remote command execution. This issue affects Apache Dubbo Apache Dubbo 2.6.x versions prior to 2.6.12; Apache Dubbo 2.7.x versions prior to 2.7.15; Apache Dubbo 3.0.x versions prior to 3.0.5. |
| 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. |