CVE-2011-0766 json
The random number generator in the Crypto application before 2.0.2.2, and SSH before 2.0.5, as used in the Erlang/OTP ssh library before R1…
published 2011-05-31 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-0778
- cvss
- 7.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.1%
- EPSS 3.1% chance of exploitation in 30 days, percentile 87%
- public exploits
- 0
- none known
Summary
The random number generator in the Crypto application before 2.0.2.2, and SSH before 2.0.5, as used in the Erlang/OTP ssh library before R14B03, uses predictable seeds based on the current time, which makes it easier for remote attackers to guess DSA host and SSH session keys.
Patch / fix
- erlang Debian 14, Debian 13, Debian 12 1:14.b.3-dfsg-1
debian advisories DEBIAN-CVE-2011-0766
- github.com/erlang/otp@f228601 commit
- kb.cert.org/vuls/id/178990 advisory
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2011-0766 updated cvss 5.8
erlang: SSH library uses a weak random number generator
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
3.07% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.8 | AV:N/AC:L/Au:N/C:C/I:N/A:N |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
References
-
github.com
/erlang/otp/commit/f228601de45c5b53241b103af6616453c50885a5
patch
-
kb.cert.org
/vuls/id/178990
third-party-advisory, patch, us-government-resource
-
secunia.com
/advisories/44709
third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/47980
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2011-0766
- NVD CVE-2011-0766
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.