← Back to KEV catalog

CVE-2014-0160

Exploitation: active CVSS 7.5 HIGH

CVSS base score: 7.5 (High) CISA · v3.1

Score assigned by CISA's Vulnrichment program; the vendor's CVE record did not include one. Vulnrichment source record →

OpenSSL Information Disclosure Vulnerability

Vendor: OpenSSL   Product: OpenSSL

Description

The TLS and DTLS implementations in OpenSSL do not properly handle Heartbeat Extension packets, which allows remote attackers to obtain sensitive information.

Research & News Coverage

No mentions found in monitored research blogs or news feeds.

Lifecycle Timeline

Each milestone comes from a different source, so gaps between them are gaps in what those sources publish, not evidence that nothing happened. EPSS history for this CVE holds 300 points from 2022-02-05, tracked daily from 2026-09-09; earlier points are weekly, which dates a spike to within a week. Peak probability 100.0% on 2026-06-20.

Published Applicability

Red Hat CSAF/VEX 0 affected · 85 fixed · 14 not affected
CVE List v5 (CNA container) 1 affected · 0 fixed · 0 not affected

Check whether a specific version is affected →

What each source publishes about which product versions carry this vulnerability, kept as written rather than merged. Absence here means no source has published applicability data, not that nothing is affected.

Detection & Exploitation

Host / SIEM
none published

Coverage across public collections only: Nuclei and OpenVAS NVT (scan); Snort and Suricata ET Open (network); Sigma and YARA (host/SIEM); Metasploit, Exploit-DB, public GitHub repositories and NVD exploit references (exploit). Absence here means nothing public was found, not that detection is impossible.
GitHub PoC repositories are collected automatically by PoC-in-GitHub (CC0) and filtered to repositories that are still online, contain code, and are starred or at least two weeks old. They are still not vetted: some are fakes and some are malware. Treat them as evidence that code was published, not as code to run.
NVD exploit references are links NVD's analysts tag as exploits; they confirm an exploit was referenced but carry no date. This product uses data from the NVD but is not endorsed or certified by the NVD.
OpenVAS coverage derives from the Greenbone Community Feed, made available under the Open Database License (ODbL) v1.0; its individual Vulnerability Tests are licensed GNU GPL v2.

First seenToolEvidenceEarliest reference
2014-04-07 Metasploit Direct — curated exploit code OpenSSL Heartbeat (Heartbleed) Information Leak +1 more
2014-04-07 GitHub PoC Unvetted — public repository FiloSottile/Heartbleed +64 more
2014-04-08 Exploit-DB Direct — curated exploit code OpenSSL TLS Heartbeat Extension - 'Heartbleed' Memory Disclosure +3 more

Metasploit is dated by the first commit of the module file, Exploit-DB by its publication date, and GitHub repositories by their creation date. GitHub PoC repositories are filtered (still online, contain code, starred or at least two weeks old) but not vetted: some are fakes and some are malware, so they show that code was published, not that it works or is safe to run. Evidence tiers are explained on the About page.

Distribution Status

Debian · openssl bookworm 1.0.1g-1 trixie 1.0.1g-1 forky 1.0.1g-1 sid 1.0.1g-1 scope: local

Where the distribution has shipped a fix, and in which version. Green means the release has resolved it, amber that it is still open. Data from the Debian Security Tracker, used under Debian's MIT / GPLv2+ terms. Debian is upstream of several other distributions, so a fix here often precedes theirs.

Fix & Cross-References

Patch and commit links and ecosystem advisory ids as published by OSV.dev. Links are listed as published, not vetted.

CISA Assessment (Vulnrichment / SSVC)

active
yes
partial
7.5 HIGH
—
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CWE-125 — Out-of-bounds Read
2025-02-07

Federal Remediation Window (BOD 26-04)

Yes — added 2022-05-04
yes
partial control
If the asset isRemediate withinTable 1 row
Publicly exposed 3 days 2 of 16
Not publicly exposed 14 days 10 of 16

BOD 26-04 replaced the single KEV deadline of BOD 22-01 with four inputs: whether the asset is publicly exposed, KEV status, whether exploitation is automatable, and technical impact. Exposure belongs to each agency's asset, not to the CVE, so both outcomes are shown. Automatable and technical impact come from the CISA assessment above. Days are calendar days; for KEV entries the clock starts on the date it was added. Agencies make the final exposure call asset by asset, and may set shorter timelines.

D3FEND Countermeasures

Defensive techniques inferred by MITRE D3FEND from the underlying weakness (CWE-125) — general hardening and detection guidance for this weakness class, not a vendor patch for this specific CVE.

External References