# CVE-2002-2020: Hardcoded credentials in n/a

> Remote attackers can gain administrative privileges on Netgear RP114 routers by using the default password on the external interface.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-5vm4-hjfj-5frm

## What is CVE-2002-2020?

CVE-2002-2020 is a high-severity vulnerability in n/a, published on 14 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Netgear RP114 Cable/DSL Web Safe Router Firmware 3.26 uses a default administrator password and accepts admin logins on the external interface, which allows remote attackers to gain privileges if the password is not changed.

## Which versions are affected by CVE-2002-2020?

It affects 1 product.


Products: Netgear Rp114.

## How do I fix CVE-2002-2020?

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

## Is CVE-2002-2020 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-4220](https://insights.sbomify.com/CVE-2005-4220/): Denial of service in n/a (high 7.8)
- [CVE-2004-2032](https://insights.sbomify.com/CVE-2004-2032/): Security feature bypass in n/a (high 7.5)
- [CVE-2002-0127](https://insights.sbomify.com/CVE-2002-0127/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-2020 and fix it if it is affected.

What it is: CVE-2002-2020 is a high-severity vulnerability in n/a, published on 14 Jul 2005. 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-2002-2020 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-2002-2020/ (Markdown: https://insights.sbomify.com/CVE-2002-2020/index.md)
```

## Sources

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

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