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

> Local attackers can capture cleartext PINs from Xircom REX 6000 devices by monitoring serial communications during PDA synchronization.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2005
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-wfxh-w5c9-96vw

## What is CVE-2001-1520?

CVE-2001-1520 is a low-severity vulnerability in n/a, published on 14 Jul 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Xircom REX 6000 allows local users to obtain the 10 digit PIN by starting a serial monitor, connecting to the personal digital assistant (PDA) via Rextools, and capturing the cleartext PIN.

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

It affects 1 product.


Products: Intel Xircom Rex 6000.

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

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

## Is CVE-2001-1520 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2001-1520 is a low-severity vulnerability in n/a, published on 14 Jul 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2001-1520 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-1520/ (Markdown: https://insights.sbomify.com/CVE-2001-1520/index.md)
```

## Sources

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

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