# CVE-2005-0065: Denial of service in n/a

> Attackers can forge ICMP error messages to disrupt TCP connections, causing denial of service or reduced throughput.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jan 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-whr2-cjwc-wj5g

## What is CVE-2005-0065?

CVE-2005-0065 is a critical denial of service vulnerability in n/a, published on 19 Jan 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 sent but not acknowledged (aka "TCP sequence number checking"), 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.

## Which versions are affected by CVE-2005-0065?

It affects 1 product.


Products: Tcp Tcp.

## How do I fix CVE-2005-0065?

No fix has been published for CVE-2005-0065 yet. Limit exposure of the affected software until one is available.

## Is CVE-2005-0065 being exploited?

There is no known exploitation of CVE-2005-0065 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2005-3675](https://insights.sbomify.com/CVE-2005-3675/): Denial of service in n/a (high 7.8)
- [CVE-2005-0066](https://insights.sbomify.com/CVE-2005-0066/): Denial of service in n/a (medium 5.0)
- [CVE-2005-0067](https://insights.sbomify.com/CVE-2005-0067/): Denial of service in n/a (medium 5.0)
- [CVE-2005-0068](https://insights.sbomify.com/CVE-2005-0068/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0065 and fix it if it is affected.

What it is: CVE-2005-0065 is a critical denial of service vulnerability in n/a, published on 19 Jan 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-0065 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2005-0065/ (Markdown: https://insights.sbomify.com/CVE-2005-0065/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2005-0065
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2005-0065
- OSV: https://osv.dev/vulnerability/CVE-2005-0065

---
From sbomify Insights: https://insights.sbomify.com/CVE-2005-0065/
Summaries are generated and may contain mistakes; the official description above is the record.