Process crash or code execution via terminator overrun
Published Jan 23, 2020 · Updated Aug 6, 2024
Stack-based buffer overflow in LibreSSL before 2.3.1 allows remote attackers to crash processes or execute arbitrary code. When the output buffer is exhausted, OBJ_obj2txt error handling writes a NUL byte through buf[0] after buf has advanced beyond the buffer. Certificate decoding reaches the function automatically on clients and on servers requesting client authentication; versions 2.0.5 and later require a BIGNUM allocation failure to enter the final error path.
Summary
What happened
Stack-based buffer overflow in LibreSSL before 2.3.1 allows remote attackers to crash processes or execute arbitrary code. When the output buffer is exhausted, OBJ_obj2txt error handling writes a NUL byte through buf[0] after buf has advanced beyond the buffer. Certificate decoding reaches the function automatically on clients and on servers requesting client authentication; versions 2.0.5 and later require a BIGNUM allocation failure to enter the final error path.
The record
- CVE
- CVE-2015-5334
- Published
- Jan 23, 2020
- Updated
- Aug 6, 2024
- Vendor
- OpenBSD Project
- Product
- LibreSSL
- Classifications
- CWE-787, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 23, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=before 2.3.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Qualys crafted-certificate trigger analysisproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo