Process crash via unchecked private-key length
Published Jun 6, 2023 · Updated Jan 8, 2025
Heap buffer overflow in axTLS 2.1.5 private-key parsing allows local users to crash the hosting process with a crafted private key. asn1_get_private_key passes unchecked values from asn1_get_big_int to RSA_priv_key_new, allowing bi_import to read beyond a heap allocation when the data and length disagree. Exploitation requires the target application to load an attacker-supplied private key, and the demonstrated consequence is process termination.
Summary
What happened
Heap buffer overflow in axTLS 2.1.5 private-key parsing allows local users to crash the hosting process with a crafted private key. asn1_get_private_key passes unchecked values from asn1_get_big_int to RSA_priv_key_new, allowing bi_import to read beyond a heap allocation when the data and length disagree. Exploitation requires the target application to load an attacker-supplied private key, and the demonstrated consequence is process termination.
The record
- CVE
- CVE-2023-33613
- Published
- Jun 6, 2023
- Updated
- Jan 8, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 6, 2023CVE publishedPublication date reported by the CVE source.
- Jan 8, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- POC10 crafted private-key reproducerproof 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