PatchTheCVEtcp vulnerabilities
Recent CVEs affecting tcp products. 6 tracked.
tcp has 6 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2005-11-18. Highest priority: CVE-2005-0065 (score 55/100).
- CVE-2005-3675 HIGH 7.8 MITIGATE The Transmission Control Protocol (TCP) allows remote attackers to cause a denial of service (bandwidth consum
- CVE-2005-0068 MEDIUM 5.0 MITIGATE The original design of ICMP does not require authentication for host-generated ICMP error messages, which make
- CVE-2005-0067 MEDIUM 5.0 MITIGATE The original design of TCP does not require that port numbers be assigned randomly (aka "Port randomization"),
- CVE-2005-0066 MEDIUM 5.0 MITIGATE The original design of TCP does not check that the TCP Acknowledgement number in an ICMP error message generat
- CVE-2005-0065 HIGH 10.0 MITIGATE The original design of TCP does not check that the TCP sequence number in an ICMP error message is within the
- CVE-2004-1060 MEDIUM 5.0 MITIGATE MITIGATE Multiple TCP/IP and ICMP implementations, when using Path MTU (PMTU) discovery (PMTUD), allow remote attackers
FAQ
How do I fix tcp vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is tcp being exploited right now?
None of the tracked tcp CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which tcp CVE should I patch first?
CVE-2005-0065 currently ranks highest (55/100): The original design of TCP does not check that the TCP sequence number in an ICMP error message is within the .