# CVE-2008-3605: Weak cryptography in n/a

> Remote attackers can perform offline brute force attacks on encrypted USB drives if the password reuse threshold is enabled, potentially exposing data.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 12 Aug 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3mjh-87v6-2677

## What is CVE-2008-3605?

CVE-2008-3605 is a medium-severity vulnerability in n/a, published on 12 Aug 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unspecified vulnerability in McAfee Encrypted USB Manager 3.1.0.0, when the Re-use Threshold for passwords is nonzero, allows remote attackers to conduct offline brute force attacks via unknown vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2008-3605?

It affects 1 product.


Products: Mcafee Encrypted Usb Manager.

## How do I fix CVE-2008-3605?

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

## Is CVE-2008-3605 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-3605 and fix it if it is affected.

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

## Sources

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

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