Overview 109 matches · 38 protected · 9 exploited · 5 CISA KEV · 16 public PoC · 12 EPSS ≥ 0.5
Protected by Waratek
38
34.9%
Rule in development
0
0.0%
Mitigation candidate
7
6.4%
No exploit published
64
58.7%
blocked by ARMR today
38
34.9%
partly blocked
0
0.0%
not blocked
71
65.1%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 24 / quarter
Q4 217
Protected by Waratek5
No exploit published2
Critical4
Medium3
blocked by ARMR today5
not blocked2
Exploited4
No public exploit3
Q1 2224
Protected by Waratek11
No exploit published13
Critical4
High3
Medium16
Low1
blocked by ARMR today11
not blocked13
Working exploit published1
Proof of concept only4
No public exploit19
Q2 229
Protected by Waratek6
Mitigation candidate1
No exploit published2
Critical1
High4
Medium3
Low1
blocked by ARMR today6
not blocked3
Working exploit published1
Proof of concept only1
No public exploit7
Q3 2217
Protected by Waratek3
Mitigation candidate2
No exploit published12
Critical1
High7
Medium7
Low2
blocked by ARMR today3
not blocked14
Exploited1
Proof of concept only3
No public exploit13
Q4 2213
Protected by Waratek3
No exploit published10
Critical1
High9
Medium3
blocked by ARMR today3
not blocked10
Exploited1
Proof of concept only4
No public exploit8
Q1 231
No exploit published1
High1
not blocked1
No public exploit1
Q2 239
Protected by Waratek5
No exploit published4
High2
Medium4
Low3
blocked by ARMR today5
not blocked4
Proof of concept only1
No public exploit8
Q3 2310
Protected by Waratek1
Mitigation candidate1
No exploit published8
High1
Medium4
Low5
blocked by ARMR today1
not blocked9
Proof of concept only1
No public exploit9
Q4 236
Protected by Waratek1
Mitigation candidate2
No exploit published3
Critical2
High2
Medium2
blocked by ARMR today1
not blocked5
Exploited2
Working exploit published1
No public exploit3
Q1 246
Protected by Waratek1
Mitigation candidate1
No exploit published4
High3
Medium3
blocked by ARMR today1
not blocked5
Proof of concept only3
No public exploit3
Q2 244
Protected by Waratek1
No exploit published3
Low4
blocked by ARMR today1
not blocked3
No public exploit4
Q3 240
Q4 241
No exploit published1
Critical1
not blocked1
No public exploit1
Q1 252
Protected by Waratek1
No exploit published1
Critical1
Medium1
blocked by ARMR today1
not blocked1
Exploited1
No public exploit1
Q1 22Q3 22Q1 23Q3 23Q1 24Q3 24Q1 25
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-21248 | Low | 2022-01-19 | Protected by Waratek | No public exploit | Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Serialization). Supported versions that are affected are Oracle Java SE: 7u321, 8u311, 11.0.13, 17.0.1; Oracle GraalVM Enterprise Edition: 20.3.4 and 21.3.0. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Java SE, Oracle GraalVM Enterprise Edition accessible data. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability can also be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. CVSS 3.1 Base Score 3.7 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N). |
| 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. |
| CVE-2021-44832 | Medium | 2021-12-28 | Protected by Waratek | Exploited | Apache Log4j2 versions 2.0-beta7 through 2.17.0 (excluding security fix releases 2.3.2 and 2.12.4) are vulnerable to a remote code execution (RCE) attack when a configuration uses a JDBC Appender with a JNDI LDAP data source URI when an attacker has control of the target LDAP server. This issue is fixed by limiting JNDI data source names to the java protocol in Log4j2 versions 2.17.1, 2.12.4, and 2.3.2. |
| CVE-2021-45105 | Medium | 2021-12-18 | Protected by Waratek | Exploited | Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1. |
| CVE-2021-23450 | Critical | 2021-12-17 | No exploit published | No public exploit | All versions of package dojo are vulnerable to Prototype Pollution via the setObject function. |
| CVE-2021-43113 | Critical | 2021-12-15 | Protected by Waratek | No public exploit | iTextPDF in iText 7 and up to (excluding 4.4.13.3) 7.1.17 allows command injection via a CompareTool filename that is mishandled on the gs (aka Ghostscript) command line in GhostscriptHelper.java. |
| CVE-2021-45046 | Critical | 2021-12-14 | Protected by Waratek | Exploited | It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default. |
| CVE-2021-44228 | Critical | 2021-12-10 | Protected by Waratek | Exploited | Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects. |
| CVE-2021-43797 | Medium | 2021-12-09 | No exploit published | No public exploit | Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients. Netty prior to version 4.1.71.Final skips control chars when they are present at the beginning / end of the header name. It should instead fail fast as these are not allowed by the spec and could lead to HTTP request smuggling. Failing to do the validation might cause netty to "sanitize" header names before it forward these to another remote system when used as proxy. This remote system can't see the invalid usage anymore, and therefore does not do the validation itself. Users should upgrade to version 4.1.71.Final. |