Remote memory exhaustion via ASN.1 OID leak
Published Jan 23, 2020 · Updated Aug 6, 2024
Memory leak in LibreSSL before 2.3.1 allows remote attackers to cause denial of service via large ASN.1 object identifier sets in X.509 certificates. OBJ_obj2txt allocates decimal strings for large subidentifiers but frees only the final temporary value, so repeated identifiers accumulate leaked memory during certificate decoding. The attack requires a service that processes attacker-supplied X.509 certificates; sufficient requests can exhaust process memory and interrupt service without granting data access or code execution.
Summary
What happened
Memory leak in LibreSSL before 2.3.1 allows remote attackers to cause denial of service via large ASN.1 object identifier sets in X.509 certificates. OBJ_obj2txt allocates decimal strings for large subidentifiers but frees only the final temporary value, so repeated identifiers accumulate leaked memory during certificate decoding. The attack requires a service that processes attacker-supplied X.509 certificates; sufficient requests can exhaust process memory and interrupt service without granting data access or code execution.
The record
- CVE
- CVE-2015-5333
- Published
- Jan 23, 2020
- Updated
- Aug 6, 2024
- Vendor
- OpenBSD Project
- Product
- LibreSSL
- Classifications
- CWE-400, 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
No public exploit references are available in this record.
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