# CVE-2010-0223: Security feature bypass in n/a

> Physically proximate attackers can bypass password protection on Kingston USB drives by replaying captured keys to access cleartext data.

- **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:** 7 Jan 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pc5r-gv46-hg46

## What is CVE-2010-0223?

CVE-2010-0223 is a low-severity vulnerability in n/a, published on 7 Jan 2010. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Kingston DataTraveler BlackBox (DTBB), DataTraveler Secure Privacy Edition (DTSP), and DataTraveler Elite Privacy Edition (DTEP) USB flash drives do not prevent password replay attacks, which allows physically proximate attackers to access the cleartext drive contents by providing a key that was captured in a USB data stream at an earlier time.

Weakness: CWE-264

## Which versions are affected by CVE-2010-0223?

It affects 3 products.


Products: Kingston Datatraveler Blackbox, Kingston Datatraveler Elite, Kingston Datatraveler Secure.

## How do I fix CVE-2010-0223?

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

## Is CVE-2010-0223 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-0222](https://insights.sbomify.com/CVE-2010-0222/): Hardcoded credentials in n/a (medium 4.6)
- [CVE-2010-0221](https://insights.sbomify.com/CVE-2010-0221/): Security feature bypass in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0223 and fix it if it is affected.

What it is: CVE-2010-0223 is a low-severity vulnerability in n/a, published on 7 Jan 2010. 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-2010-0223 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-2010-0223/ (Markdown: https://insights.sbomify.com/CVE-2010-0223/index.md)
```

## Sources

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

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