# CVE-2004-0641: Other in n/a

> Remote attackers can spoof or hijack TCP connections due to predictable Initial Sequence Numbers in Thomson SpeedTouch 510 routers.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-c2xh-jwfq-qgr6

## What is CVE-2004-0641?

CVE-2004-0641 is a high-severity vulnerability in n/a, published on 14 Apr 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Thomson SpeedTouch 510 ADSL Router with firmware GV8BAA3.270, and possibly earlier versions, generates predictable TCP Initial Sequence Numbers (ISNs), which allows remote attackers to spoof or hijack TCP connections.

## Which versions are affected by CVE-2004-0641?

It affects 1 product.


Products: Thomson Speedtouch.

## How do I fix CVE-2004-0641?

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

## Is CVE-2004-0641 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-0641 exists.

Public exploit code:

- Linux Kernel 2.2 - Predictable TCP Initial Sequence Number (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-0947](https://insights.sbomify.com/CVE-2006-0947/): Missing authorization in n/a (high 7.5)
- [CVE-2007-6003](https://insights.sbomify.com/CVE-2007-6003/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2006-0946](https://insights.sbomify.com/CVE-2006-0946/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0641 and fix it if it is affected.

What it is: CVE-2004-0641 is a high-severity vulnerability in n/a, published on 14 Apr 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-0641 exists.

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-2004-0641/ (Markdown: https://insights.sbomify.com/CVE-2004-0641/index.md)
```

## Sources

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

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