CVE-2004-0641
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThomson 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Thomson SpeedTouch 510 ADSL Router with firmware GV8BAA3.270 and possibly earlier versions generates predictable TCP Initial Sequence Numbers (ISNs) using a weak pseudo-random number generation algorithm. Attackers can predict future ISNs and forge TCP packets to spoof or hijack existing TCP connections, bypassing authentication mechanisms that rely on TCP session integrity.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 510_adsl_routerCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm router model is Thomson SpeedTouch 510Log into the router web interface (typically 192.168.1.1) or check the device label/marketing materials to verify the exact model number.Affected if The device is a Thomson SpeedTouch 510 ADSL router.
-
Check installed firmware versionAccess the router administration panel, typically via web browser at the default gateway. Navigate to the status or system information page to view the firmware revision. The version string often appears as something like GV8BAA3.270.Affected if The firmware version is GV8BAA3.270 or earlier (including unknown versions on the 510 model).
-
Verify network exposure of the deviceDetermine if the router's WAN/Internet interface is directly accessible from external networks. Check router port forwarding rules, firewall settings, or perform an external port scan targeting the router's WAN IP on common management ports (HTTP/HTTPS).Affected if The router is accessible from untrusted networks and uses the vulnerable firmware.
-
Assess whether TCP-based authentication is in useReview any systems or applications that rely on TCP session integrity or source IP authentication for security (such as IP-based access controls, stateful firewall rules expecting TCP handshake integrity, or legacy protocols using TCP for authentication).Affected if Security mechanisms depend on unpredictable TCP sequence numbers and the router firmware is vulnerable.
A user is affected if they operate a Thomson SpeedTouch 510 router with firmware GV8BAA3.270 or earlier that is accessible on a network where TCP session integrity is relied upon for security.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade the router firmware to a version that implements cryptographically secure random ISN generation, or replace the legacy device with a modern router that properly randomizes TCP sequence numbers.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-0641 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2004-0641 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data