CVE-2002-2380
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 · uneditedNetDSL ADSL Modem 800 with Microsoft Network firmware 5.5.11 allows remote attackers to gain access to configuration menus by sniffing undocumented usernames and passwords from network traffic.
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 NetDSL ADSL Modem 800 with Microsoft Network firmware 5.5.11 transmits undocumented usernames and passwords across the network in an insecure manner (likely cleartext or weakly encoded), allowing remote attackers who can sniff network traffic to capture these credentials and gain administrative access to the modem's configuration interface.
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= 5.5.11CVSS 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
- None
AV:N/AC:L/Au:N/C:P/I:P/A:N
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 device model is NetDSL ADSL Modem 800Access the device's web interface or administrative console and identify the exact model number. This is typically displayed on the status page or in the device information section of the web-based configuration.Affected if The device model is NetDSL ADSL Modem 800
-
Verify firmware version is 5.5.11Check the firmware or software version displayed in the device's administrative interface, typically found under System Info, Status, or About sections. Compare your installed version to the affected range (5.5.11).Affected if The installed firmware version is exactly 5.5.11
-
Confirm remote administration is enabledAccess the device's web configuration and locate the remote management or administration settings. Verify whether remote HTTP/HTTPS access to the administrative interface is permitted from external network locations.Affected if Remote administration is enabled and accessible from outside the local network
-
Inspect network traffic for credential exposureUse a network packet capture tool (such as Wireshark) to monitor HTTP traffic to and from the modem's administrative interface. Look for usernames and passwords transmitted in cleartext or with weak encoding during authentication or configuration operations.Affected if Authentication credentials are transmitted in cleartext or weakly encoded format in network traffic
A user is affected if they are running the NetDSL ADSL Modem 800 with Microsoft Network firmware version 5.5.11 and the device's administrative interface is accessible remotely, with credentials transmitted insecurely over the network.
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 dataReplace the end-of-life modem with a currently-supported device, as firmware updates are unavailable for this 2002 product. If the device must remain in service, change any default credentials, disable remote administration where possible, and segment the device on a restricted VLAN.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-2380 — 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-2380 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