CVE-2002-0119
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 · uneditedAlcatel Speed Touch Home ADSL Modem allows remote attackers to cause a denial of service (reboot) via a network scan with unusual packets, such as nmap with OS detection.
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 · moderate confidenceThe Alcatel Speed Touch Home ADSL Modem can be forced to reboot when subjected to a network scan using unusual packets, such as those generated by nmap with OS detection enabled. This represents a denial-of-service vulnerability where the device's firmware improperly handles certain network probe packets, causing a reboot rather than gracefully handling or ignoring the unexpected input.
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 dataall versionsCVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Identify Alcatel Speed Touch Home device on networkCheck network documentation, DHCP lease tables, or physically inspect network equipment for an Alcatel Speed Touch Home ADSL modemAffected if The device model matches Alcatel Speed Touch Home
-
Confirm device is powered on and accessiblePing the IP address assigned to the modem or attempt to access its web management interface on the typical HTTP portsAffected if The device responds to network requests and is an Alcatel Speed Touch Home
-
Verify device firmware versionAccess the modem web interface or check the device label for any firmware version markingsAffected if Any firmware version is present on the Alcatel Speed Touch Home (all versions are affected)
-
Assess network exposureDetermine if the modem management interface is exposed to untrusted networks or the internetAffected if The modem is directly reachable from networks outside the local administrative zone
If an Alcatel Speed Touch Home ADSL modem is present and network-accessible on your environment, it is affected by this vulnerability regardless of firmware version.
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 dataSince this vulnerability affects legacy hardware from 2002, the recommended remediation is to replace the affected Alcatel Speed Touch Home modem with a current device, as this hardware is likely end-of-life and unlikely to receive firmware patches. If replacement is not immediately feasible, network segmentation can be used to restrict access to the device.
- Consultation4.0 h
- Implementation8.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 $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0119 — 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-2002-0119 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