Overview 27 matches · 0 in Waratek scope · 0 protected · 2 exploited · 1 CISA KEV · 2 public PoC · 0 EPSS ≥ 0.5
27matches
0in Waratek scope0.0%
0protected0.0%
2exploited7.4%
1CISA KEV3.7%
2public PoC7.4%
0EPSS ≥ 0.50.0%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
1
3.7%
Not applicable
26
96.3%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
27
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
2
7.4%
Working exploit published
0
0.0%
Proof of concept only
2
7.4%
Forecast only
0
0.0%
No public exploit
23
85.2%
split by
peak 20 / quarter
Q2 2020
Outside Waratek scope1
Not applicable19
Critical6
High3
Medium11
not blocked20
Exploited2
Proof of concept only2
No public exploit16
Q3 200
Q4 201
Not applicable1
Critical1
not blocked1
No public exploit1
Q1 210
Q2 210
Q3 213
Not applicable3
Critical1
High2
not blocked3
No public exploit3
Q4 210
Q1 222
Not applicable2
High1
Medium1
not blocked2
No public exploit2
Q2 220
Q3 220
Q4 220
Q1 230
Q2 230
Q3 230
Q4 230
Q1 240
Q2 241
Not applicable1
Medium1
not blocked1
No public exploit1
Q2 20Q4 20Q2 21Q4 21Q2 22Q4 22Q2 23Q4 23Q2 24
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2024-28957 | Medium | 2024-04-15 | Not applicable | No public exploit | Generation of predictable identifiers issue exists in Cente middleware TCP/IP Network Series. If this vulnerability is exploited, a remote unauthenticated attacker may interfere communications by predicting some packet header IDs of the device. |
| CVE-2022-23083 | Medium | 2022-01-18 | Not applicable | No public exploit | NetMaster 12.2 Network Management for TCP/IP and NetMaster File Transfer Management contain a XSS (Cross-Site Scripting) vulnerability in ReportCenter UI due to insufficient input validation that could potentially allow an attacker to execute code on the affected machine. |
| CVE-2021-45445 | High | 2022-01-12 | Not applicable | No public exploit | Unisys ClearPath MCP TCP/IP Networking Services 59.1, 60.0, and 62.0 has an Infinite Loop. |
| CVE-2020-25928 | Critical | 2021-08-18 | Not applicable | No public exploit | The DNS feature in InterNiche NicheStack TCP/IP 4.0.1 is affected by: Buffer Overflow. The impact is: execute arbitrary code (remote). The component is: DNS response processing functions: dns_upcall(), getoffset(), dnc_set_answer(). The attack vector is: a specific DNS response packet. The code does not check the "response data length" field of individual DNS answers, which may cause out-of-bounds read/write operations, leading to Information leak, Denial-or-Service, or Remote Code Execution, depending on the context. |
| CVE-2020-25927 | High | 2021-08-18 | Not applicable | No public exploit | The DNS feature in InterNiche NicheStack TCP/IP 4.0.1 is affected by: Out-of-bounds Read. The impact is: a denial of service (remote). The component is: DNS response processing in function: dns_upcall(). The attack vector is: a specific DNS response packet. The code does not check whether the number of queries/responses specified in the DNS packet header corresponds to the query/response data available in the DNS packet. |
| CVE-2020-25926 | High | 2021-08-18 | Not applicable | No public exploit | The DNS client in InterNiche NicheStack TCP/IP 4.0.1 is affected by: Insufficient entropy in the DNS transaction id. The impact is: DNS cache poisoning (remote). The component is: dns_query_type(). The attack vector is: a specific DNS response packet. |
| CVE-2020-25066 | Critical | 2020-12-22 | Not applicable | No public exploit | A heap-based buffer overflow in the Treck HTTP Server component before 6.0.1.68 allows remote attackers to cause a denial of service (crash/reset) or to possibly execute arbitrary code. |
| CVE-2020-11914 | Medium | 2020-06-17 | Not applicable | No public exploit | The Treck TCP/IP stack before 6.0.1.66 has an ARP Out-of-bounds Read. |
| CVE-2020-11913 | Medium | 2020-06-17 | Not applicable | No public exploit | The Treck TCP/IP stack before 6.0.1.66 has an IPv6 Out-of-bounds Read. |
| CVE-2020-11912 | Medium | 2020-06-17 | Not applicable | No public exploit | The Treck TCP/IP stack before 6.0.1.66 has a TCP Out-of-bounds Read. |
| CVE-2020-11911 | Medium | 2020-06-17 | Not applicable | No public exploit | The Treck TCP/IP stack before 6.0.1.66 has Improper ICMPv4 Access Control. |
| CVE-2020-11910 | Critical | 2020-06-17 | Not applicable | No public exploit | The Treck TCP/IP stack before 6.0.1.66 has an ICMPv4 Out-of-bounds Read. |
| CVE-2020-11909 | Critical | 2020-06-17 | Not applicable | No public exploit | The Treck TCP/IP stack before 6.0.1.66 has an IPv4 Integer Underflow. |
| CVE-2020-11908 | Medium | 2020-06-17 | Not applicable | No public exploit | The Treck TCP/IP stack before 4.7.1.27 mishandles '\0' termination in DHCP. |
| CVE-2020-11907 | Medium | 2020-06-17 | Not applicable | No public exploit | The Treck TCP/IP stack before 6.0.1.66 improperly handles a Length Parameter Inconsistency in TCP. |
| CVE-2020-11906 | Medium | 2020-06-17 | Not applicable | No public exploit | The Treck TCP/IP stack before 6.0.1.66 has an Ethernet Link Layer Integer Underflow. |
| CVE-2020-11905 | Medium | 2020-06-17 | Not applicable | No public exploit | The Treck TCP/IP stack before 6.0.1.66 has a DHCPv6 Out-of-bounds Read. |
| CVE-2020-11904 | High | 2020-06-17 | Not applicable | No public exploit | The Treck TCP/IP stack before 6.0.1.66 has an Integer Overflow during Memory Allocation that causes an Out-of-Bounds Write. |
| CVE-2020-11903 | Medium | 2020-06-17 | Not applicable | No public exploit | The Treck TCP/IP stack before 6.0.1.28 has a DHCP Out-of-bounds Read. |
| CVE-2020-11902 | High | 2020-06-17 | Not applicable | No public exploit | The Treck TCP/IP stack before 6.0.1.66 has an IPv6OverIPv4 tunneling Out-of-bounds Read. |
| CVE-2020-11901 | Critical | 2020-06-17 | Not applicable | No public exploit | The Treck TCP/IP stack before 6.0.1.66 allows Remote Code execution via a single invalid DNS response. |
| CVE-2020-11900 | High | 2020-06-17 | Not applicable | Exploited | The Treck TCP/IP stack before 6.0.1.41 has an IPv4 tunneling Double Free. |
| CVE-2020-11899 | Medium | 2020-06-17 | Not applicable | Exploited | The Treck TCP/IP stack before 6.0.1.66 has an IPv6 Out-of-bounds Read. |
| CVE-2020-11898 | Critical | 2020-06-17 | Not applicable | No public exploit | The Treck TCP/IP stack before 6.0.1.66 improperly handles an IPv4/ICMPv4 Length Parameter Inconsistency, which might allow remote attackers to trigger an information leak. |
| CVE-2020-11897 | Critical | 2020-06-17 | Not applicable | No public exploit | The Treck TCP/IP stack before 5.0.1.35 has an Out-of-Bounds Write via multiple malformed IPv6 packets. |
| CVE-2020-11896 | Critical | 2020-06-17 | Not applicable | Proof of concept only | The Treck TCP/IP stack before 6.0.1.66 allows Remote Code Execution, related to IPv4 tunneling. |
| CVE-2020-10136 | Medium | 2020-06-02 | Outside Waratek scope | Proof of concept only | IP-in-IP protocol specifies IP Encapsulation within IP standard (RFC 2003, STD 1) that decapsulate and route IP-in-IP traffic is vulnerable to spoofing, access-control bypass and other unexpected behavior due to the lack of validation to verify network packets before decapsulation and routing. |