Overview 13 matches · 4 in Waratek scope · 3 protected · 2 exploited · 0 CISA KEV · 2 public PoC · 4 EPSS ≥ 0.5
13matches
4in Waratek scope30.8%
3protected23.1%
2exploited15.4%
0CISA KEV0.0%
2public PoC15.4%
4EPSS ≥ 0.530.8%
Protected by Waratek
3
23.1%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
1
7.7%
Outside Waratek scope
6
46.2%
Not applicable
3
23.1%
Withdrawn CVE
0
0.0%
blocked by ARMR today
3
23.1%
partly blocked
0
0.0%
not blocked
10
76.9%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
2
15.4%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
3
23.1%
No public exploit
8
61.5%
split by
peak 8 / year
20111
Not applicable1
High1
not blocked1
No public exploit1
20120
20130
20140
20150
20160
20170
20180
20190
20201
Outside Waratek scope1
High1
not blocked1
No public exploit1
20218
Protected by Waratek1
No exploit published1
Outside Waratek scope5
Not applicable1
High8
blocked by ARMR today1
not blocked7
Exploited2
Forecast only1
No public exploit5
20222
Protected by Waratek2
High2
blocked by ARMR today2
Forecast only2
20231
Not applicable1
High1
not blocked1
No public exploit1
2011201320152017201920212023
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2023-28166 | High | 2023-06-22 | Not applicable | No public exploit | Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in Aakif Kadiwala Tags Cloud Manager plugin <= 1.0.0 versions. |
| CVE-2022-23307 | High | 2022-01-18 | Protected by Waratek | Forecast only | CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists. |
| CVE-2022-23302 | High | 2022-01-18 | Protected by Waratek | Forecast only | JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. 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-4104 | High | 2021-12-14 | Protected by Waratek | Exploited | JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. 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-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-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-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-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-2011-2654 | High | 2011-09-06 | Not applicable | No public exploit | The RPC implementation in the server in Novell Cloud Manager 1.1.2 before Patch 3 does not properly initialize objects, which allows remote attackers to execute arbitrary code by making RPC calls that leverage incorrect privileges associated with a partially initialized session. |