# CVE-2001-1210: Misconfiguration in n/a

> Remote attackers can read and write MIB data on Cisco DOCSIS routers due to unrestricted SNMP access with arbitrary community strings.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 15 Mar 2002
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-q9rh-f7ch-2g23

## What is CVE-2001-1210?

CVE-2001-1210 is a medium-severity vulnerability in n/a, published on 15 Mar 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco ubr900 series routers that conform to the Data-over-Cable Service Interface Specifications (DOCSIS) standard must ship without SNMP access restrictions, which can allow remote attackers to read and write information to the MIB using arbitrary community strings.

## Which versions are affected by CVE-2001-1210?

It affects 3 products.


Products: Cisco Ubr920, Cisco Ubr924, Cisco Ubr925.

## How do I fix CVE-2001-1210?

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

## Is CVE-2001-1210 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1210 and fix it if it is affected.

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

## Sources

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

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