Overview 16 matches · 3 in Waratek scope · 1 protected · 0 exploited · 0 CISA KEV · 4 EPSS ≥ 0.5
Protected by Waratek
1
6.2%
Rule in development
0
0.0%
Mitigation candidate
2
12.5%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
13
81.2%
Withdrawn CVE
0
0.0%
blocked by ARMR today
1
6.2%
partly blocked
0
0.0%
not blocked
15
93.8%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
16
100.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
0
0.0%
split by
peak 2 / year
19982
Not applicable2
High1
Low1
not blocked2
Working exploit published2
19991
Not applicable1
Medium1
not blocked1
Working exploit published1
20002
Not applicable2
High1
Medium1
not blocked2
Working exploit published2
20011
Not applicable1
High1
not blocked1
Working exploit published1
20021
Not applicable1
Medium1
not blocked1
Working exploit published1
20030
20040
20050
20060
20072
Not applicable2
Medium2
not blocked2
Working exploit published2
20081
Not applicable1
Medium1
not blocked1
Working exploit published1
20090
20100
20110
20120
20130
20140
20150
20160
20171
Not applicable1
High1
not blocked1
Working exploit published1
20180
20191
Not applicable1
High1
not blocked1
Working exploit published1
20202
Protected by Waratek1
Not applicable1
High2
blocked by ARMR today1
not blocked1
Working exploit published2
20212
Mitigation candidate2
High2
not blocked2
Working exploit published2
199920012003200520072009201120132015201720192021
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2021-39146 | High | 2021-08-23 | Mitigation candidate | Working exploit published | XStream is a simple library to serialize objects to XML and back again. In affected versions this vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. XStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose. |
| CVE-2021-39141 | High | 2021-08-23 | Mitigation candidate | Working exploit published | XStream is a simple library to serialize objects to XML and back again. In affected versions this vulnerability may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. XStream 1.4.18 uses no longer a blacklist by default, since it cannot be secured for general purpose. |
| CVE-2020-9484 | High | 2020-05-20 | Protected by Waratek | Working exploit published | When using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a) an attacker is able to control the contents and name of a file on the server; and b) the server is configured to use the PersistenceManager with a FileStore; and c) the PersistenceManager is configured with sessionAttributeValueClassNameFilter="null" (the default unless a SecurityManager is used) or a sufficiently lax filter to allow the attacker provided object to be deserialized; and d) the attacker knows the relative file path from the storage location used by FileStore to the file the attacker has control over; then, using a specifically crafted request, the attacker will be able to trigger remote code execution via deserialization of the file under their control. Note that all of conditions a) to d) must be true for the attack to succeed. |
| CVE-2020-8617 | High | 2020-05-19 | Not applicable | Working exploit published | Using a specially-crafted message, an attacker may potentially cause a BIND server to reach an inconsistent state if the attacker knows (or successfully guesses) the name of a TSIG key used by the server. Since BIND, by default, configures a local session key even on servers whose configuration does not otherwise make use of it, almost all current BIND servers are vulnerable. In releases of BIND dating from March 2018 and after, an assertion check in tsig.c detects this inconsistent state and deliberately exits. Prior to the introduction of the check the server would continue operating in an inconsistent state, with potentially harmful results. |
| CVE-2017-3141 | High | 2019-01-16 | Not applicable | Working exploit published | The BIND installer on Windows uses an unquoted service path which can enable a local user to achieve privilege escalation if the host file system permissions allow this. Affects BIND 9.2.6-P2->9.2.9, 9.3.2-P1->9.3.6, 9.4.0->9.8.8, 9.9.0->9.9.10, 9.10.0->9.10.5, 9.11.0->9.11.1, 9.9.3-S1->9.9.10-S1, 9.10.5-S1. |
| CVE-2017-8779 | High | 2017-05-04 | Not applicable | Working exploit published | rpcbind through 0.2.4, LIBTIRPC through 1.0.1 and 1.0.2-rc through 1.0.2-rc3, and NTIRPC through 1.4.3 do not consider the maximum RPC data size during memory allocation for XDR strings, which allows remote attackers to cause a denial of service (memory consumption with no subsequent free) via a crafted UDP packet to port 111, aka rpcbomb. |
| CVE-2008-1447 | Medium | 2008-07-08 | Not applicable | Working exploit published | The DNS protocol, as implemented in (1) BIND 8 and 9 before 9.5.0-P1, 9.4.2-P1, and 9.3.5-P1; (2) Microsoft DNS in Windows 2000 SP4, XP SP2 and SP3, and Server 2003 SP1 and SP2; and other implementations allow remote attackers to spoof DNS traffic via a birthday attack that uses in-bailiwick referrals to conduct cache poisoning against recursive resolvers, related to insufficient randomness of DNS transaction IDs and source ports, aka "DNS Insufficient Socket Entropy Vulnerability" or "the Kaminsky bug." |
| CVE-2007-2930 | Medium | 2007-09-12 | Not applicable | Working exploit published | The (1) NSID_SHUFFLE_ONLY and (2) NSID_USE_POOL PRNG algorithms in ISC BIND 8 before 8.4.7-P1 generate predictable DNS query identifiers when sending outgoing queries such as NOTIFY messages when answering questions as a resolver, which allows remote attackers to poison DNS caches via unknown vectors. NOTE: this issue is different from CVE-2007-2926. |
| CVE-2007-2926 | Medium | 2007-07-24 | Not applicable | Working exploit published | ISC BIND 9 through 9.5.0a5 uses a weak random number generator during generation of DNS query ids when answering resolver questions or sending NOTIFY messages to slave name servers, which makes it easier for remote attackers to guess the next query id and perform DNS cache poisoning. |
| CVE-2002-1220 | Medium | 2002-11-29 | Not applicable | Working exploit published | BIND 8.3.x through 8.3.3 allows remote attackers to cause a denial of service (termination due to assertion failure) via a request for a subdomain that does not exist, with an OPT resource record with a large UDP payload size. |
| CVE-2001-0010 | High | 2001-02-12 | Not applicable | Working exploit published | Buffer overflow in transaction signature (TSIG) handling code in BIND 8 allows remote attackers to gain root privileges. |
| CVE-2000-0887 | Medium | 2000-12-19 | Not applicable | Working exploit published | named in BIND 8.2 through 8.2.2-P6 allows remote attackers to cause a denial of service by making a compressed zone transfer (ZXFR) request and performing a name service query on an authoritative record that is not cached, aka the "zxfr bug." |
| CVE-2000-1029 | High | 2000-12-11 | Not applicable | Working exploit published | Buffer overflow in host command allows a remote attacker to execute arbitrary commands via a long response to an AXFR query. |
| CVE-1999-0848 | Medium | 1999-11-10 | Not applicable | Working exploit published | Denial of service in BIND named via consuming more than "fdmax" file descriptors. |
| CVE-1999-1499 | Low | 1998-04-10 | Not applicable | Working exploit published | named in ISC BIND 4.9 and 8.1 allows local users to destroy files via a symlink attack on (1) named_dump.db when root kills the process with a SIGINT, or (2) named.stats when SIGIOT is used. |
| CVE-1999-0009 | High | 1998-04-08 | Not applicable | Working exploit published | Inverse query buffer overflow in BIND 4.9 and BIND 8 Releases. |