Treck TCP/IP stack
CVEs (8)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2020-11898 | Cri | 0.61 | 9.1 | 0.19 | Jun 17, 2020 | 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-11899 | Med | 0.49 | 5.4 | 0.19 | KEV | Jun 17, 2020 | The Treck TCP/IP stack before 6.0.1.66 has an IPv6 Out-of-bounds Read. | |
| CVE-2020-11904 | Hig | 0.48 | 7.3 | 0.03 | Jun 17, 2020 | 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-11902 | Hig | 0.48 | 7.3 | 0.09 | Jun 17, 2020 | The Treck TCP/IP stack before 6.0.1.66 has an IPv6OverIPv4 tunneling Out-of-bounds Read. | ||
| CVE-2020-11905 | Med | 0.42 | 6.5 | 0.02 | Jun 17, 2020 | The Treck TCP/IP stack before 6.0.1.66 has a DHCPv6 Out-of-bounds Read. | ||
| CVE-2020-11903 | Med | 0.42 | 6.5 | 0.02 | Jun 17, 2020 | The Treck TCP/IP stack before 6.0.1.28 has a DHCP Out-of-bounds Read. | ||
| CVE-2020-11907 | Med | 0.41 | 6.3 | 0.02 | Jun 17, 2020 | The Treck TCP/IP stack before 6.0.1.66 improperly handles a Length Parameter Inconsistency in TCP. | ||
| CVE-2020-11913 | Med | 0.35 | 5.3 | 0.03 | Jun 17, 2020 | The Treck TCP/IP stack before 6.0.1.66 has an IPv6 Out-of-bounds Read. |
- risk 0.61cvss 9.1epss 0.19
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.
- risk 0.49cvss 5.4epss 0.19
The Treck TCP/IP stack before 6.0.1.66 has an IPv6 Out-of-bounds Read.
- risk 0.48cvss 7.3epss 0.03
The Treck TCP/IP stack before 6.0.1.66 has an Integer Overflow during Memory Allocation that causes an Out-of-Bounds Write.
- risk 0.48cvss 7.3epss 0.09
The Treck TCP/IP stack before 6.0.1.66 has an IPv6OverIPv4 tunneling Out-of-bounds Read.
- risk 0.42cvss 6.5epss 0.02
The Treck TCP/IP stack before 6.0.1.66 has a DHCPv6 Out-of-bounds Read.
- risk 0.42cvss 6.5epss 0.02
The Treck TCP/IP stack before 6.0.1.28 has a DHCP Out-of-bounds Read.
- risk 0.41cvss 6.3epss 0.02
The Treck TCP/IP stack before 6.0.1.66 improperly handles a Length Parameter Inconsistency in TCP.
- risk 0.35cvss 5.3epss 0.03
The Treck TCP/IP stack before 6.0.1.66 has an IPv6 Out-of-bounds Read.