# CVE-2009-3278: Weak cryptography in n/a

> Weak random number generation in QNAP NAS firmware allows local attackers to brute-force recovery keys, bypassing security controls.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qx3r-xm4v-rgrh

## What is CVE-2009-3278?

CVE-2009-3278 is a medium-severity vulnerability in n/a, published on 21 Sep 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The QNAP TS-239 Pro and TS-639 Pro with firmware 2.1.7 0613, 3.1.0 0627, and 3.1.1 0815 use the rand library function to generate a certain recovery key, which makes it easier for local users to determine this key via a brute-force attack.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

## Which versions are affected by CVE-2009-3278?

It affects 2 products.


Products: Qnap Ts-239 Pro Firmware, Qnap Ts-639 Pro Firmware.

## How do I fix CVE-2009-3278?

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

## Is CVE-2009-3278 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3278 and fix it if it is affected.

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

## Sources

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

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