Process termination via hash-table memory exhaustion
Published May 3, 2022 · Updated May 5, 2025
Resource exhaustion in OpenSSL 3.0.0 through 3.0.2 allows remote attackers to interrupt long-lived processes through repeated decoding. OPENSSL_LH_flush clears every hash bucket but leaves lh->num_items unchanged, so later reuse treats removed entries as live and repeatedly grows the table. Exposure requires a long-lived process that repeatedly decodes certificates or keys, such as a TLS client or a server accepting client certificates; exhaustion slows traversal and can terminate the process.
Summary
What happened
Resource exhaustion in OpenSSL 3.0.0 through 3.0.2 allows remote attackers to interrupt long-lived processes through repeated decoding. OPENSSL_LH_flush clears every hash bucket but leaves lh->num_items unchanged, so later reuse treats removed entries as live and repeatedly grows the table. Exposure requires a long-lived process that repeatedly decodes certificates or keys, such as a TLS client or a server accepting client certificates; exhaustion slows traversal and can terminate the process.
The record
- CVE
- CVE-2022-1473
- Published
- May 3, 2022
- Updated
- May 5, 2025
- Vendor
- OpenSSL Project
- Product
- OpenSSL
- Classifications
- CWE-459, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 3, 2022CVE publishedPublication date reported by the CVE source.
- May 5, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2)
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