CVE-2005-0067
Last modified
CVE-2005-0067 is a vulnerability of currently unknown severity. The original design of TCP does not require that port numbers be assigned randomly (aka "Port randomization"), which makes it easier for attackers to forge ICMP error messages for specific TCP connections and cause a denial of service, as demonstrated using (1) blind connection-reset attacks with forged "Destination Unreachable" messages, (2) blind throughput-reduction attacks with forged "Source Quench" messages, or (3) blind throughput-reduction attacks with forged ICMP messages that cause the Path MTU to be reduced. NOTE: CVE-2004-0790, CVE-2004-0791, and CVE-2004-1060 have been SPLIT based on different attacks; CVE-2005-0065, CVE-2005-0066, CVE-2005-0067, and CVE-2005-0068 are related identifiers that are SPLIT based on the underlying vulnerability. EPSS estimates a 13.46% chance of exploitation in the next 30 days.
Description
The original design of TCP does not require that port numbers be assigned randomly (aka "Port randomization"), which makes it easier for attackers to forge ICMP error messages for specific TCP connections and cause a denial of service, as demonstrated using (1) blind connection-reset attacks with forged "Destination Unreachable" messages, (2) blind throughput-reduction attacks with forged "Source Quench" messages, or (3) blind throughput-reduction attacks with forged ICMP messages that cause the Path MTU to be reduced. NOTE: CVE-2004-0790, CVE-2004-0791, and CVE-2004-1060 have been SPLIT based on different attacks; CVE-2005-0065, CVE-2005-0066, CVE-2005-0067, and CVE-2005-0068 are related identifiers that are SPLIT based on the underlying vulnerability. While CVE normally SPLITs based on vulnerability, the attack-based identifiers exist due to the variety and number of affected implementations and solutions that address the attacks instead of the underlying vulnerabilities.
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Tcp | Tcp | All versions |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2005-0067?
How severe is CVE-2005-0067?
How do I fix CVE-2005-0067?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2005
- CVE-2005-0060Buffer overflow in the font processing component of Microsof…
- CVE-2005-0061The kernel of Microsoft Windows 2000, Windows XP SP1 and SP2…
- CVE-2005-0063The document processing application used by the Windows Shel…
- CVE-2005-0064Buffer overflow in the Decrypt::makeFileKey2 function in Dec…
- CVE-2005-0065The original design of TCP does not check that the TCP seque…
- CVE-2005-0066The original design of TCP does not check that the TCP Ackno…
- CVE-2005-0068The original design of ICMP does not require authentication …
- CVE-2005-0069The (1) tcltags or (2) vimspell.sh scripts in vim 6.3 allow …
- CVE-2005-0070Synaesthesia 2.1 and earlier, and possibly other versions, w…
- CVE-2005-0071vdr before 1.2.6 does not securely create files, which allow…
- CVE-2005-0072zhcon before 0.2 does not drop privileges before reading a u…
- CVE-2005-0073Buffer overflow in queue.c in a support script for sympa 3.3…
Are you affected by CVE-2005-0067?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
