# CVE-2001-1221: Hardcoded credentials in n/a

> Remote attackers can access sensitive information via the default SNMP community string on D-Link DWL-1000AP devices.

- **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:** 15 Mar 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-j6r7-c7cv-j6gw

## What is CVE-2001-1221?

CVE-2001-1221 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

D-Link DWL-1000AP Firmware 3.2.28 #483 Wireless LAN Access Point uses a default SNMP community string of 'public' which allows remote attackers to gain sensitive information.

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

It affects 1 product.


Products: D-Link Dwl-1000ap.

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

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

## Is CVE-2001-1221 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-1220](https://insights.sbomify.com/CVE-2001-1220/): Hardcoded credentials in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-1221 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-1221 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-1221/ (Markdown: https://insights.sbomify.com/CVE-2001-1221/index.md)
```

## Sources

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

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