Overview 11 matches · 0 in Waratek scope · 0 protected · 2 exploited · 0 CISA KEV · 1 public PoC · 2 EPSS ≥ 0.5
11matches
0in Waratek scope0.0%
0protected0.0%
2exploited18.2%
0CISA KEV0.0%
1public PoC9.1%
2EPSS ≥ 0.518.2%
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
0
0.0%
Not applicable
11
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
11
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
2
18.2%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
1
9.1%
No public exploit
8
72.7%
split by
peak 11 / month
Aug 19
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2019-12262 | Critical | 2019-08-14 | Not applicable | No public exploit | Wind River VxWorks 6.6, 6.7, 6.8, 6.9 and 7 has Incorrect Access Control in the RARP client component. IPNET security vulnerability: Handling of unsolicited Reverse ARP replies (Logical Flaw). |
| CVE-2019-12265 | Medium | 2019-08-09 | Not applicable | No public exploit | Wind River VxWorks 6.5, 6.6, 6.7, 6.8, 6.9.3 and 6.9.4 has a Memory Leak in the IGMPv3 client component. There is an IPNET security vulnerability: IGMP Information leak via IGMPv3 specific membership report. |
| CVE-2019-12263 | High | 2019-08-09 | Not applicable | Exploited | Wind River VxWorks 6.9.4 and vx7 has a Buffer Overflow in the TCP component (issue 4 of 4). There is an IPNET security vulnerability: TCP Urgent Pointer state confusion due to race condition. |
| CVE-2019-12261 | Critical | 2019-08-09 | Not applicable | No public exploit | Wind River VxWorks 6.7 though 6.9 and vx7 has a Buffer Overflow in the TCP component (issue 3 of 4). This is an IPNET security vulnerability: TCP Urgent Pointer state confusion during connect() to a remote host. |
| CVE-2019-12260 | Critical | 2019-08-09 | Not applicable | No public exploit | Wind River VxWorks 6.9 and vx7 has a Buffer Overflow in the TCP component (issue 2 of 4). This is an IPNET security vulnerability: TCP Urgent Pointer state confusion caused by a malformed TCP AO option. |
| CVE-2019-12259 | High | 2019-08-09 | Not applicable | No public exploit | Wind River VxWorks 6.6, 6.7, 6.8, 6.9 and vx7 has an array index error in the IGMPv3 client component. There is an IPNET security vulnerability: DoS via NULL dereference in IGMP parsing. |
| CVE-2019-12258 | High | 2019-08-09 | Not applicable | No public exploit | Wind River VxWorks 6.6 through vx7 has Session Fixation in the TCP component. This is a IPNET security vulnerability: DoS of TCP connection via malformed TCP options. |
| CVE-2019-12257 | High | 2019-08-09 | Not applicable | Forecast only | Wind River VxWorks 6.6 through 6.9 has a Buffer Overflow in the DHCP client component. There is an IPNET security vulnerability: Heap overflow in DHCP Offer/ACK parsing inside ipdhcpc. |
| CVE-2019-12256 | Critical | 2019-08-09 | Not applicable | No public exploit | Wind River VxWorks 6.9 and vx7 has a Buffer Overflow in the IPv4 component. There is an IPNET security vulnerability: Stack overflow in the parsing of IPv4 packets’ IP options. |
| CVE-2019-12255 | Critical | 2019-08-09 | Not applicable | Exploited | Wind River VxWorks has a Buffer Overflow in the TCP component (issue 1 of 4). This is a IPNET security vulnerability: TCP Urgent Pointer = 0 that leads to an integer underflow. |
| CVE-2019-12264 | High | 2019-08-05 | Not applicable | No public exploit | Wind River VxWorks 6.6, 6.7, 6.8, 6.9.3, 6.9.4, and Vx7 has Incorrect Access Control in IPv4 assignment by the ipdhcpc DHCP client component. |