CVE-2005-0065

The original design of TCP does not check that the TCP sequence number in an ICMP error message is within the range of sequence numbers for data that has been…

published January 19, 2005

CVSS
—
EPSS
2%
Percentile
79.8
In the wild
Unconfirmed
What it is

⚠️ An attacker can forge ICMP error messages due to a missing TCP sequence number check, like slipping past security with a fake ID! Think of TCP as a busy restaurant: your order (data packets) needs to be acknowledged by the kitchen (receiver) before you can place new ones. If a mischievous diner (attacker) sends in a forged note pretending to be from the kitchen, they can mess up everyone’s dining experience by cancelling orders or reducing portions — that's how this vulnerability wreaks havoc! If exploited, this vulnerability allows attackers to cause denial of service by resetting connections or reducing throughput, effectively slowing down or interrupting your network operations. It's like having a patron disrupt the flow of service and ruin the dining experience for everyone else at the restaurant!

Put simply

Think of TCP as a busy restaurant: your order (data packets) needs to be acknowledged by the kitchen (receiver) before you can place new ones. If a mischievous diner (attacker) sends in a forged note pretending to be from the kitchen, they can mess up everyone’s dining experience by cancelling orders or reducing portions — that's how this vulnerability wreaks havoc! The vulnerability arises from the original design of TCP not verifying that TCP sequence numbers in ICMP error messages correspond to acknowledged packets. As a result, attackers can send forged ICMP messages that disrupt ongoing TCP connections.

What to do

If exploited, this vulnerability allows attackers to cause denial of service by resetting connections or reducing throughput, effectively slowing down or interrupting your network operations. It's like having a patron disrupt the flow of service and ruin the dining experience for everyone else at the restaurant! To remediate this issue, ensure your TCP stack checks sequence numbers in ICMP messages properly. Regular updates to your networking software and firewalls can help mitigate this risk, and consider implementing rate limiting on ICMP traffic to further protect your systems. This may sound complex, but with the right updates and configurations, you can ensure your TCP connections are safe and sound! 🛡️

The record
Technical detail
CVSS
Not scored
CVSS v4.0
Not supplied
EPSS
0.01937 · 79.8th percentile
Published
2005-01-19T05:00Z
EPSS history
Timeline
  • 19 JAN 05:00Z
    The original design of TCP does not check that the TCP sequence number in an ICMP error message is within the range of sequence numbers for data that has been…
    cvelistv5