Overview 21 matches · 7 in Waratek scope · 5 protected · 4 exploited · 2 CISA KEV · 4 public PoC · 6 EPSS ≥ 0.5
21matches
7in Waratek scope33.3%
5protected23.8%
4exploited19.0%
2CISA KEV9.5%
4public PoC19.0%
6EPSS ≥ 0.528.6%
Protected by Waratek
5
23.8%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
2
9.5%
Outside Waratek scope
12
57.1%
Not applicable
2
9.5%
Withdrawn CVE
0
0.0%
blocked by ARMR today
5
23.8%
partly blocked
0
0.0%
not blocked
16
76.2%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
4
19.0%
Working exploit published
1
4.8%
Proof of concept only
0
0.0%
Forecast only
2
9.5%
No public exploit
14
66.7%
split by
peak 7 / quarter
Q2 161
Protected by Waratek1
Critical1
blocked by ARMR today1
Exploited1
Q3 160
Q4 160
Q1 170
Q2 170
Q3 170
Q4 170
Q1 180
Q2 180
Q3 180
Q4 180
Q1 190
Q2 190
Q3 190
Q4 190
Q1 201
Not applicable1
Critical1
not blocked1
No public exploit1
Q2 201
Outside Waratek scope1
High1
not blocked1
No public exploit1
Q3 200
Q4 200
Q1 215
Outside Waratek scope4
Not applicable1
Critical1
High4
not blocked5
Exploited1
No public exploit4
Q2 217
Protected by Waratek1
No exploit published2
Outside Waratek scope4
High2
Medium4
Low1
blocked by ARMR today1
not blocked6
Working exploit published1
Forecast only2
No public exploit4
Q3 212
Outside Waratek scope2
Medium2
not blocked2
No public exploit2
Q4 214
Protected by Waratek3
Outside Waratek scope1
Critical1
High1
Medium2
blocked by ARMR today3
not blocked1
Exploited2
No public exploit2
Q2 16Q4 16Q2 17Q4 17Q2 18Q4 18Q2 19Q4 19Q2 20Q4 20Q2 21Q4 21
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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-42550 | Medium | 2021-12-16 | Protected by Waratek | No public exploit | In logback version 1.2.7 and prior versions, an attacker with the required privileges to edit configurations files could craft a malicious configuration allowing to execute arbitrary code loaded from LDAP servers. |
| 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-27002 | High | 2021-10-11 | Outside Waratek scope | No public exploit | NetApp Cloud Manager versions prior to 3.9.10 are susceptible to a vulnerability which could allow a remote unauthenticated attacker to retrieve sensitive data via the web proxy. |
| CVE-2021-26999 | Medium | 2021-08-06 | Outside Waratek scope | No public exploit | NetApp Cloud Manager versions prior to 3.9.9 log sensitive information when an Active Directory connection fails. The logged information is available only to authenticated users. Customers with auto-upgrade enabled should already be on a fixed version while customers using on-prem connectors with auto-upgrade disabled are advised to upgrade to a fixed version. |
| CVE-2021-26998 | Medium | 2021-08-06 | Outside Waratek scope | No public exploit | NetApp Cloud Manager versions prior to 3.9.9 log sensitive information that is available only to authenticated users. Customers with auto-upgrade enabled should already be on a fixed version while customers using on-prem connectors with auto-upgrade disabled are advised to upgrade to a fixed version. |
| CVE-2021-31807 | Medium | 2021-06-08 | Outside Waratek scope | No public exploit | An issue was discovered in Squid before 4.15 and 5.x before 5.0.6. An integer overflow problem allows a remote server to achieve Denial of Service when delivering responses to HTTP Range requests. The issue trigger is a header that can be expected to exist in HTTP traffic without any malicious intent. |
| CVE-2021-31808 | Medium | 2021-05-27 | Outside Waratek scope | No public exploit | An issue was discovered in Squid before 4.15 and 5.x before 5.0.6. Due to an input-validation bug, it is vulnerable to a Denial of Service attack (against all clients using the proxy). A client sends an HTTP Range request to trigger this. |
| CVE-2021-31806 | Medium | 2021-05-27 | Outside Waratek scope | Forecast only | An issue was discovered in Squid before 4.15 and 5.x before 5.0.6. Due to a memory-management bug, it is vulnerable to a Denial of Service attack (against all clients using the proxy) via HTTP Range request processing. |
| CVE-2021-28651 | High | 2021-05-27 | Outside Waratek scope | No public exploit | An issue was discovered in Squid before 4.15 and 5.x before 5.0.6. Due to a buffer-management bug, it allows a denial of service. When resolving a request with the urn: scheme, the parser leaks a small amount of memory. However, there is an unspecified attack methodology that can easily trigger a large amount of memory consumption. |
| CVE-2021-28165 | High | 2021-04-01 | No exploit published | Forecast only | In Eclipse Jetty 7.2.2 to 9.4.38, 10.0.0.alpha0 to 10.0.1, and 11.0.0.alpha0 to 11.0.1, CPU usage can reach 100% upon receiving a large invalid TLS frame. |
| CVE-2021-28164 | Medium | 2021-04-01 | Protected by Waratek | Working exploit published | In Eclipse Jetty 9.4.37.v20210219 to 9.4.38.v20210224, the default compliance mode allows requests with URIs that contain %2e or %2e%2e segments to access protected resources within the WEB-INF directory. For example a request to /context/%2e/WEB-INF/web.xml can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application. |
| CVE-2021-28163 | Low | 2021-04-01 | No exploit published | No public exploit | In Eclipse Jetty 9.4.32 to 9.4.38, 10.0.0.beta2 to 10.0.1, and 11.0.0.beta2 to 11.0.1, if a user uses a webapps directory that is a symlink, the contents of the webapps directory is deployed as a static webapp, inadvertently serving the webapps themselves and anything else that might be in that directory. |
| CVE-2021-26992 | High | 2021-03-19 | Outside Waratek scope | No public exploit | Cloud Manager versions prior to 3.9.4 are susceptible to a vulnerability which could allow a remote attacker to cause a Denial of Service (DoS). |
| CVE-2021-26991 | High | 2021-03-19 | Outside Waratek scope | No public exploit | Cloud Manager versions prior to 3.9.4 contain an insecure Cross-Origin Resource Sharing (CORS) policy which could allow a remote attacker to interact with Cloud Manager. |
| CVE-2021-26990 | Critical | 2021-03-19 | Outside Waratek scope | No public exploit | Cloud Manager versions prior to 3.9.4 are susceptible to a vulnerability that could allow a remote attacker to overwrite arbitrary system files. |
| CVE-2020-25097 | High | 2021-03-19 | Outside Waratek scope | No public exploit | An issue was discovered in Squid through 4.13 and 5.x through 5.0.4. Due to improper input validation, it allows a trusted client to perform HTTP Request Smuggling and access services otherwise forbidden by the security controls. This occurs for certain uri_whitespace configuration settings. |
| CVE-2021-23337 | High | 2021-02-15 | Not applicable | Exploited | Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function. |
| CVE-2020-14058 | High | 2020-06-30 | Outside Waratek scope | No public exploit | An issue was discovered in Squid before 4.12 and 5.x before 5.0.3. Due to use of a potentially dangerous function, Squid and the default certificate validation helper are vulnerable to a Denial of Service when opening a TLS connection to an attacker-controlled server for HTTPS. This occurs because unrecognized error values are mapped to NULL, but later code expects that each error value is mapped to a valid error string. |
| CVE-2019-17275 | Critical | 2020-02-26 | Not applicable | No public exploit | OnCommand Cloud Manager versions prior to 3.8.0 are susceptible to arbitrary code execution by remote attackers. |
| CVE-2016-3427 | Critical | 2016-04-21 | Protected by Waratek | Exploited | Unspecified vulnerability in Oracle Java SE 6u113, 7u99, and 8u77; Java SE Embedded 8u77; and JRockit R28.3.9 allows remote attackers to affect confidentiality, integrity, and availability via vectors related to JMX. |