Focus on treck vulnerabilities and metrics.
Last updated: 08 Mar 2025, 23:25 UTC
This page consolidates all known Common Vulnerabilities and Exposures (CVEs) associated with treck. We track both calendar-based metrics (using fixed periods) and rolling metrics (using gliding windows) to give you a comprehensive view of security trends and risk evolution. Use these insights to assess risk and plan your patching strategy.
For a broader perspective on cybersecurity threats, explore the comprehensive list of CVEs by vendor and product. Stay updated on critical vulnerabilities affecting major software and hardware providers.
Total treck CVEs: 20
Earliest CVE date: 02 Jun 2020, 09:15 UTC
Latest CVE date: 22 Dec 2020, 22:15 UTC
Latest CVE reference: CVE-2020-25066
30-day Count (Rolling): 0
365-day Count (Rolling): 0
Calendar-based Variation
Calendar-based Variation compares a fixed calendar period (e.g., this month versus the same month last year), while Rolling Growth Rate uses a continuous window (e.g., last 30 days versus the previous 30 days) to capture trends independent of calendar boundaries.
Month Variation (Calendar): 0%
Year Variation (Calendar): 0%
Month Growth Rate (30-day Rolling): 0.0%
Year Growth Rate (365-day Rolling): 0.0%
Average CVSS: 5.92
Max CVSS: 10.0
Critical CVEs (≥9): 3
| Range | Count |
|---|---|
| 0.0-3.9 | 4 |
| 4.0-6.9 | 10 |
| 7.0-8.9 | 3 |
| 9.0-10.0 | 3 |
These are the five CVEs with the highest CVSS scores for treck, sorted by severity first and recency.
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.
The Treck TCP/IP stack before 6.0.1.66 has an ARP Out-of-bounds Read.
The Treck TCP/IP stack before 6.0.1.66 has an IPv6 Out-of-bounds Read.
The Treck TCP/IP stack before 6.0.1.66 has a TCP Out-of-bounds Read.
The Treck TCP/IP stack before 6.0.1.66 has Improper ICMPv4 Access Control.
The Treck TCP/IP stack before 6.0.1.66 has an ICMPv4 Out-of-bounds Read.
The Treck TCP/IP stack before 6.0.1.66 has an IPv4 Integer Underflow.
The Treck TCP/IP stack before 6.0.1.66 improperly handles a Length Parameter Inconsistency in TCP.
The Treck TCP/IP stack before 6.0.1.66 has an Ethernet Link Layer Integer Underflow.
The Treck TCP/IP stack before 6.0.1.66 has a DHCPv6 Out-of-bounds Read.
The Treck TCP/IP stack before 6.0.1.66 has an Integer Overflow during Memory Allocation that causes an Out-of-Bounds Write.
The Treck TCP/IP stack before 6.0.1.28 has a DHCP Out-of-bounds Read.
The Treck TCP/IP stack before 6.0.1.66 has an IPv6OverIPv4 tunneling Out-of-bounds Read.
The Treck TCP/IP stack before 6.0.1.66 allows Remote Code execution via a single invalid DNS response.
The Treck TCP/IP stack before 6.0.1.41 has an IPv4 tunneling Double Free.
The Treck TCP/IP stack before 6.0.1.66 has an IPv6 Out-of-bounds Read.
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.
The Treck TCP/IP stack before 5.0.1.35 has an Out-of-Bounds Write via multiple malformed IPv6 packets.
The Treck TCP/IP stack before 6.0.1.66 allows Remote Code Execution, related to IPv4 tunneling.
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.