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

> Remote attackers can read or write MIB information on DOCSIS cable modems using the default public SNMP community string.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2005
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-73mm-2mw9-vjgg

## What is CVE-2002-2112?

CVE-2002-2112 is a medium-severity vulnerability in n/a, published on 5 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

RCA Digital Cable Modem DCM225 and DCM225E, and other modems that must conform to the Data-over-Cable Service Interface Specifications DOCSIS standard, uses the "public" community string for SNMP access, which allows remote attackers to read or write MIB information.

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

It affects 1 product.


Products: Rca Digital Cable Modem.

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

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

## Is CVE-2002-2112 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-2110](https://insights.sbomify.com/CVE-2002-2110/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-2112 is a medium-severity vulnerability in n/a, published on 5 Aug 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-2112 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-2112/ (Markdown: https://insights.sbomify.com/CVE-2002-2112/index.md)
```

## Sources

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

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