Overview 10 matches · 3 in Waratek scope · 3 protected · 1 exploited · 0 CISA KEV · 3 public PoC · 5 EPSS ≥ 0.5
10matches
3in Waratek scope30.0%
3protected30.0%
1exploited10.0%
0CISA KEV0.0%
3public PoC30.0%
5EPSS ≥ 0.550.0%
Protected by Waratek
3
30.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
6
60.0%
Not applicable
1
10.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
3
30.0%
partly blocked
0
0.0%
not blocked
7
70.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
1
10.0%
Working exploit published
2
20.0%
Proof of concept only
0
0.0%
Forecast only
2
20.0%
No public exploit
5
50.0%
split by
peak 3 / year
20151
Outside Waratek scope1
High1
not blocked1
Working exploit published1
20160
20171
Outside Waratek scope1
High1
not blocked1
Working exploit published1
20181
Outside Waratek scope1
High1
not blocked1
No public exploit1
20190
20203
Outside Waratek scope3
High3
not blocked3
No public exploit3
20212
Protected by Waratek1
Not applicable1
High2
blocked by ARMR today1
not blocked1
Exploited1
No public exploit1
20222
Protected by Waratek2
High2
blocked by ARMR today2
Forecast only2
20152016201720182019202020212022
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| 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-2020-28895 | High | 2021-02-03 | Not applicable | No public exploit | In Wind River VxWorks, memory allocator has a possible overflow in calculating the memory block's size to be allocated by calloc(). As a result, the actual memory allocated is smaller than the buffer size specified by the arguments, leading to memory corruption. |
| CVE-2020-12723 | High | 2020-06-05 | Outside Waratek scope | No public exploit | regcomp.c in Perl before 5.30.3 allows a buffer overflow via a crafted regular expression because of recursive S_study_chunk calls. |
| CVE-2020-10878 | High | 2020-06-05 | Outside Waratek scope | No public exploit | Perl before 5.30.3 has an integer overflow related to mishandling of a "PL_regkind[OP(n)] == NOTHING" situation. A crafted regular expression could lead to malformed bytecode with a possibility of instruction injection. |
| CVE-2020-10543 | High | 2020-06-05 | Outside Waratek scope | No public exploit | Perl before 5.30.3 on 32-bit platforms allows a heap-based buffer overflow because nested regular expression quantifiers have an integer overflow. |
| CVE-2018-7566 | High | 2018-03-30 | Outside Waratek scope | No public exploit | The Linux kernel 4.15 has a Buffer Overflow via an SNDRV_SEQ_IOCTL_SET_CLIENT_POOL ioctl write operation to /dev/snd/seq by a local user. |
| CVE-2017-3730 | High | 2017-05-04 | Outside Waratek scope | Working exploit published | In OpenSSL 1.1.0 before 1.1.0d, if a malicious server supplies bad parameters for a DHE or ECDHE key exchange then this can result in the client attempting to dereference a NULL pointer leading to a client crash. This could be exploited in a Denial of Service attack. |
| CVE-2015-0235 | High | 2015-01-28 | Outside Waratek scope | Working exploit published | Heap-based buffer overflow in the __nss_hostname_digits_dots function in glibc 2.2, and other 2.x versions before 2.18, allows context-dependent attackers to execute arbitrary code via vectors related to the (1) gethostbyname or (2) gethostbyname2 function, aka "GHOST." |