Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2014-0160 is a high-severity Out-of-bounds Read (CWE-125) vulnerability in Mitel Micollab. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 0.0% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
The vulnerability CVE-2014-0160 is a buffer over-read (CWE-125) in the TLS and DTLS implementations of OpenSSL versions 1.0.1 through 1.0.1f. It stems from improper handling of Heartbeat Extension packets in the files d1_both.c and t1_lib.c, which fails to validate the length of incoming packets before reading from process memory.
Remote attackers with network access can exploit the flaw by sending specially crafted Heartbeat requests, triggering an out-of-bounds read that discloses up to 64 KB of sensitive data such as private keys, session cookies, or other process memory contents. The attack requires no authentication and can be repeated to increase the volume of leaked data, as reflected in the CVSS 7.5 score emphasizing high confidentiality impact without affecting integrity or availability.
Advisories and patches referenced in the provided URLs, including the OpenSSL git commit 96db9023b881d7cd9f379b0c154650d6c108e9a3, indicate that the issue is resolved by upgrading to OpenSSL 1.0.1g, with distribution-specific guidance such as MGASA-2014-0165 recommending immediate updates to the patched package.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2014-0217
Vulnerability Data
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…
more
by reading private keys, related to d1_both.c and t1_lib.c, aka the Heartbleed bug.
- CWE(s)
- KEV Date Added
- 04 May 2022
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices such as bounds checking and memory-safe languages directly prevent out-of-bounds reads.
Vulnerability scanning and recording can discover instances of out-of-bounds reads after code is deployed.
Routine patching replaces vulnerable code containing out-of-bounds read flaws.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance includes fuzzing and static analysis that detect out-of-bounds read defects before release.
Logging can record evidence of an out-of-bounds read but does not prevent the weakness itself.
Secure development life cycle mandates input validation and bounds checking that directly prevent out-of-bounds reads.
Application security requirements include explicit bounds and memory-safety specifications that mitigate buffer over-reads.
Secure system architecture and engineering principles require memory-safe design patterns and runtime protections against out-of-bounds access.
Secure coding standards explicitly forbid unsafe pointer arithmetic and mandate bounds-checked reads, eliminating CWE-125.