# CVE-2001-0514: Missing authorization in n/a

> Remote attackers can access sensitive WEP keys and cause denial of service on Atmel-based wireless access points due to missing authorization checks.

- **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:** 9 Mar 2002
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-75j3-qq88-rrpc

## What is CVE-2001-0514?

CVE-2001-0514 is a high-severity missing authorization vulnerability in n/a, published on 9 Mar 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SNMP service in Atmel 802.11b VNET-B Access Point 1.3 and earlier, as used in Netgear ME102 and Linksys WAP11, accepts arbitrary community strings with requested MIB modifications, which allows remote attackers to obtain sensitive information such as WEP keys, cause a denial of service, or gain access to the network.

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

It affects 3 products.


Products: Atmel 802.11b Vnet-B Access Point, Linksys Wap11, Netgear Me102.

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

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

## Is CVE-2001-0514 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2001-0514 is a high-severity missing authorization vulnerability in n/a, published on 9 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-0514 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-0514/ (Markdown: https://insights.sbomify.com/CVE-2001-0514/index.md)
```

## Sources

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

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