CVE-2014-0160
OpenSSL Information Disclosure Vulnerability
OpenSSL OpenSSL
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remote attackers to obtain sensitive information from process memory via crafted packets that trigger a buffer over-read, as demonstrated by reading private keys, related to d1_both.c and t1_lib.c, aka the Heartbleed bug.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 4 May 2022. US federal agencies were required to remediate it by 25 May 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 100%, which is higher than 99.9% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Frequently asked questions
Is CVE-2014-0160 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2014-0160.
What does CVE-2014-0160 affect?
CVE-2014-0160 affects OpenSSL OpenSSL. The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remote attackers to obtain sensitive information from process memory via crafted packets that trigger a buffer over-read, as demonstrated by reading private keys, related to d1_both.c and t1_lib.c, aka the Heartbleed bug.
How severe is CVE-2014-0160?
CVE-2014-0160 is rated HIGH with a CVSS base score of 7.5. EPSS puts the probability of exploitation in the next 30 days at 100%, higher than 99.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 25 May 2022.
How should organisations respond to CVE-2014-0160?
Apply the vendor patch for OpenSSL OpenSSL as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.