# CVE-2004-0680: Auth bypass in n/a

> Remote attackers can bypass authentication on Zoom X3 ADSL modems by using default credentials on the terminal port, gaining unauthorized administrative access.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-gr6r-mw69-wm7r

## What is CVE-2004-0680?

CVE-2004-0680 is a critical authentication bypass vulnerability in n/a, published on 13 Jul 2004. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Zoom 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.

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

It affects 1 product.


Products: Zoom Model 5560 X3 Ethernet Adsl Modem.

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

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

## Is CVE-2004-0680 being exploited?

There is no known exploitation of CVE-2004-0680 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0680 is a critical authentication bypass vulnerability in n/a, published on 13 Jul 2004. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-0680 in the wild and no public exploit code.

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

## Sources

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

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