# CVE-2010-0228: Hardcoded credentials in n/a

> Attackers with physical access can read or modify data on Verbatim Corporate Secure USB drives by using a fixed hardcoded encryption key.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 16 Sep 2024
- **Also known as:** GHSA-cg8p-xj6f-g83m

## What is CVE-2010-0228?

CVE-2010-0228 is a medium-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

Verbatim Corporate Secure and Corporate Secure FIPS Edition USB flash drives use a fixed 256-bit key for obtaining access to the cleartext drive contents, which makes it easier for physically proximate attackers to read or modify data by determining and providing this key.

Weakness: CWE-310

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

It affects 1 product.


Products: Verbatim Corporate Secure.

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

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

## Is CVE-2010-0228 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-0227](https://insights.sbomify.com/CVE-2010-0227/): Security feature bypass in n/a (medium 4.6)
- [CVE-2010-0229](https://insights.sbomify.com/CVE-2010-0229/): Security feature bypass in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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