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

> Remote attackers can bypass authentication on 3Com OfficeConnect Remote 812 ADSL Routers by repeatedly attempting login with any credentials.

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

## What is CVE-2004-0477?

CVE-2004-0477 is a critical authentication bypass vulnerability in n/a, published on 8 Jul 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unknown vulnerability in 3Com OfficeConnect Remote 812 ADSL Router allows remote attackers to bypass authentication via repeated attempts using any username and password.  NOTE: this identifier was inadvertently re-used for another issue due to a typo; that issue was assigned CVE-2004-0447.  This candidate is ONLY for the ADSL router bypass.

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

It affects 1 product.


Products: 3com 3cp4144.

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

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

## Is CVE-2004-0477 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-0888](https://insights.sbomify.com/CVE-2002-0888/): Security feature bypass in n/a (high 7.5)
- [CVE-2004-0476](https://insights.sbomify.com/CVE-2004-0476/): Denial of service in n/a (medium 5.0)
- [CVE-2003-0291](https://insights.sbomify.com/CVE-2003-0291/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-0477 is a critical authentication bypass vulnerability in n/a, published on 8 Jul 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-0477 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-0477/ (Markdown: https://insights.sbomify.com/CVE-2004-0477/index.md)
```

## Sources

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

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