CVE-2004-0680
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 · uneditedZoom X3 ADSL modem has a terminal running on port 254 that can be accessed using the default HTML management password, even if the password has been changed for the HTTP interface, which could allow remote attackers to gain unauthorized access.
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 Zoom X3 ADSL modem has a terminal service running on port 254 that remains accessible using the default HTML management password, even after the HTTP interface password has been changed, allowing remote attackers to gain unauthorized access to the device.
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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 the device modelCheck the device label, web interface, or SNMP fingerprint for the exact model number. Confirm it is a Zoom Model 5560 X3 Ethernet Adsl Modem.Affected if The device is a Zoom Model 5560 X3
-
Scan for port 254 accessibilityUse a network scanner (such as nmap) or telnet to test if port 254 is open and accepting connections on the device IP address.Affected if Port 254 is open and reachable from an untrusted network segment
-
Verify the terminal service is presentConnect to port 254 using telnet or netcat and observe whether a login prompt or terminal interface appears.Affected if A terminal login prompt is presented on port 254
-
Test default credential accessAttempt to log in to the service on port 254 using the default HTML management password (the same default password used for the HTTP management interface).Affected if Authentication succeeds with the default password after the HTTP interface password has been changed
-
Confirm credential independenceChange the HTTP management interface password via the web UI, then verify whether the terminal service on port 254 still accepts the default password.Affected if The default password still works on port 254 even after the HTTP password was modified
The device is affected if it is a Zoom Model 5560 X3 with port 254 accessible and the default password still grants terminal access after the HTTP interface password has been changed.
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.
dbcve · scopedRestrict network access to port 254 via firewall or network segmentation; consider replacing the end-of-life device if patching is unavailable.
- Replace the Zoom X3 ADSL Modem (Model 5560 X3) with a currently-supported modem/router from a vendor that provides security updates.
- If replacement is not immediately possible, place the vulnerable device behind a firewall that blocks external access to port 254 and disable any exposed terminal services via the device's administration interface.
- Contact Zoom Technologies to verify if any firmware updates were ever released for this device; however, given the 2004 disclosure date and the age of this hardware, no fix is likely available.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2004-0680 — 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-0680 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