![]() | |
CVE identifier(s) | CVE-2014-0160 |
---|---|
Released | 1 February 2012 |
Date discovered | 1 April 2014 |
Date patched | 7 April 2014 |
Discoverer |
|
Affected software | OpenSSL (1.0.1) |
Website | heartbleed |
Heartbleed is a security bug in some outdated versions of the OpenSSL cryptography library, which is a widely used implementation of the Transport Layer Security (TLS) protocol. It was introduced into the software in 2012 and publicly disclosed in April 2014. Heartbleed could be exploited regardless of whether the vulnerable OpenSSL instance is running as a TLS server or client. It resulted from improper input validation (due to a missing bounds check) in the implementation of the TLS heartbeat extension.[5] Thus, the bug's name derived from heartbeat.[6] The vulnerability was classified as a buffer over-read,[7] a situation where more data can be read than should be allowed.[8]
Heartbleed was registered in the Common Vulnerabilities and Exposures database as CVE-2014-0160.[7] The federal Canadian Cyber Incident Response Centre issued a security bulletin advising system administrators about the bug.[9] A fixed version of OpenSSL was released on 7 April 2014, on the same day Heartbleed was publicly disclosed.[10]
TLS implementations other than OpenSSL, such as GnuTLS, Mozilla's Network Security Services, and the Windows platform implementation of TLS, were not affected because the defect existed in the OpenSSL's implementation of TLS rather than in the protocol itself.[11]
System administrators were frequently slow to patch their systems. As of 20 May 2014[update], 1.5% of the 800,000 most popular TLS-enabled websites were still vulnerable to Heartbleed.[12] As of 21 June 2014[update], 309,197 public web servers remained vulnerable.[13] As of 23 January 2017[update], according to a report[14] from Shodan, nearly 180,000 internet-connected devices were still vulnerable.[15][16] As of 6 July 2017[update], the number had dropped to 144,000, according to a search on shodan.io for "vuln:cve-2014-0160".[17] As of 11 July 2019[update], Shodan reported[18] that 91,063 devices were vulnerable. The U.S. was first with 21,258 (23%), the top 10 countries had 56,537 (62%), and the remaining countries had 34,526 (38%). The report also broke the devices down by 10 other categories such as organization (the top 3 were wireless companies), product (Apache httpd, Nginx), or service (HTTPS, 81%).
hb
was invoked but never defined (see the help page).Graham-2014-06-21
was invoked but never defined (see the help page).Shodan-report-DCPO7BkV
was invoked but never defined (see the help page).Schwartz-2017-01-30
was invoked but never defined (see the help page).MacVittie-2017-02-02
was invoked but never defined (see the help page).Carey-2017-07-10
was invoked but never defined (see the help page).