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

> Predictable random number generation in Debian's OpenSSL allows attackers to guess cryptographic keys, compromising encrypted data and authentication.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 May 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-0166, GHSA-4xrg-5554-qffr

## What is CVE-2008-0166?

CVE-2008-0166 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 13 May 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenSSL 0.9.8c-1 up to versions before 0.9.8g-9 on Debian-based operating systems uses a random number generator that generates predictable numbers, which makes it easier for remote attackers to conduct brute force guessing attacks against cryptographic keys.

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

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

It affects 3 products.


Products: Canonical Ubuntu Linux, Debian Debian Linux, Openssl Openssl.

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

Upgrade to a fixed version.

## Is CVE-2008-0166 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-0166 exists.

Public exploit code:

- Debian OpenSSL Predictable PRNG (CVE-2008-0166) (github_poc): https://github.com/g0tmi1k/debian-ssh
- Search for BTC coins on earlier versions of Bitcoin Core with critical vulnerability OpenSSL 0.9.8 CVE-2008-0166 (github_poc): https://github.com/demining/Vulnerable-to-Debian-OpenSSL-bug-CVE-2008-0166
- Private keys vulnerable to Debian OpenSSL bug (CVE-2008-0166) (github_poc): https://github.com/badkeys/debianopenssl
- Debian OpenSSL Predictable PRNG (CVE-2008-0166) (github_poc): https://github.com/avarx/vulnkeys
- OpenSSL 0.9.8c-1 < 0.9.8g-9 (Debian and Derivatives) - Predictable PRNG Brute Force SSH (exploitdb)
- OpenSSL 0.9.8c-1 < 0.9.8g-9 (Debian and Derivatives) - Predictable PRNG Brute Force SSH (Ruby) (exploitdb)

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-0166 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 13 May 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-0166 exists.

Affected product: Canonical Ubuntu Linux. 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-0166/ (Markdown: https://insights.sbomify.com/CVE-2008-0166/index.md)
```

## Sources

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

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