# CVE-2001-0352: Information disclosure in n/a

> Remote attackers can read WEP encryption keys from SNMP MIBs on 3Com and Symbol access points, compromising wireless network security.

- **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:** 27 Jul 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-669c-qgx2-q34x

## What is CVE-2001-0352?

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

### Official description

SNMP agents in 3Com AirConnect AP-4111 and Symbol 41X1 Access Point allow remote attackers to obtain the WEP encryption key by reading it from a MIB when the value should be write-only, via (1) dot11WEPDefaultKeyValue in the dot11WEPDefaultKeysTable of the IEEE 802.11b MIB, or (2) ap128bWepKeyValue in the ap128bWEPKeyTable in the Symbol MIB.

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

It affects 2 products.


Products: 3com 3crwe747a, Symbol 41x1 Access Point.

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

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

## Is CVE-2001-0352 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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