Jump to content

Draft:Debian OpenSSL vulnerability

From Wikipedia, the free encyclopedia

Debian OpenSSL vulnerability (Common Vulnerabilities and Exposures number CVE-2008-0166[1]) was a security vulnerability present exclusively in the Debian operating system and its derivatives from 2006 until it was discovered in 2008.[2][3] The vulnerability affected the random number generator provided by OpenSSL (distributed as libssl), which was used by multiple software packages for the generation of cryptographic keys and certificates. The vulnerability made it possible to only generate a small number of predictable keypairs.[4]

Background

[edit]

The vulnerability was introduced to the Debian bug team in April 2006. It was accepted a month later, while the first affected version of the libssl package (0.9.8c-1) came out on 17 September 2006.[2][3] At the time, it was viewed as a fix for warnings from the Valgrind memory debugger about the use of uninitialized memory by OpenSSL, which, unbeknownst to the bug team, served as a source entropy for its random number generator (RNG). As a result, the RNG lost practically all sources of randomness, with the exception of the PID of the process that requested its output.[4][5]

As the maximum number of PIDs was restricted to 32,768, only 32,767[a] (215 − 1) unique keys of every type and size could be generated on the affected systems.[4][5][6]

Discovery and Impact

[edit]

The vulnerability was discovered by Debian developer Luciano Bello and disclosed on 13 May 2008, security patches correcting the vulnerability were released on the same day. The patches only fixed the RNG, they would not fix already existing weak keys, all of which had to be regenerated.[3][7]

Even though other operating systems were not directly affected, importing vulnerable keys could also put them at risk.[8]

Affected software

[edit]

Operating systems
Debian-based Linux distributions using libssl versions 0.9.8c-1 through 0.9.8g-9[9], confirmed examples are:

Notable packages

Legacy

[edit]

A day before the 20th anniversary of the bug's introduction, security researcher Hanno Böck disclosed that multiple websites were actively using keys affected by this vulnerability to produce DKIM signatures for their emails.[13]

Notes

[edit]
  1. ^ In Unix-based operating systems, PID 0 is reserved for the init and cannot be used by ordinary proccesses.

References

[edit]
  1. ^ "CVE-2008-0166 Detail". National Vulnerability Database. NIST. Retrieved 6 October 2024.
  2. ^ a b "#363516 valgrind-clean the RNG". Debian bug report logs. 19 April 2006. Retrieved 6 October 2024.
  3. ^ a b c "[SECURITY] [DSA 1571-1] New openssl packages fix predictable random number generator". Debian security mailing list. 13 May 2008. Retrieved 6 October 2024.
  4. ^ a b c Garfinkel, Simson (20 May 2008). "Alarming Open-Source Security Holes". MIT Technology Review. Retrieved 6 October 2024.
  5. ^ a b Cox, Russ (21 May 2008). "Lessons from the Debian/OpenSSL Fiasco". research!rsc. Retrieved 6 October 2024.
  6. ^ Moore, H. D. "Debian OpenSSL Predictable PRNG Toys". Metasploit.com. Archived from the original on 8 June 2009. Retrieved 9 October 2024.
  7. ^ "Key Rollover". Debian Security. Archived from the original on 22 November 2008. Retrieved 6 October 2024.
  8. ^ a b c "USN-612-1: OpenSSL vulnerability". Ubuntu Security. 13 May 2008. Retrieved 6 October 2024.
  9. ^ a b "CVE-2008-0166". Debian security tracker. Retrieved 6 October 2024.
  10. ^ "USN-612-2: OpenSSH vulnerability". Ubuntu Security. 13 May 2008. Retrieved 6 October 2024.
  11. ^ "USN-612-3: OpenVPN vulnerability". Ubuntu Security. 13 May 2008. Retrieved 6 October 2024.
  12. ^ "Tor security advisory: Debian flaw causes weak identity keys". 13 May 2008. Retrieved 6 October 2024.
  13. ^ Böck, Hanno (12 May 2024). "16 years of CVE-2008-0166 Debian OpenSSL Bug - Breaking DKIM and BIMI in 2024". Retrieved 6 October 2024.

Category:Computer security exploits Category:2008 in computing