Application crash via unchecked digest initialization
Published Feb 8, 2023 · Updated Nov 4, 2025
NULL pointer dereference in PKCS7 verification in OpenSSL 3.0.0 through 3.0.7 allows attackers to crash consuming applications. The signature-verification path fails to check unsuccessful digest initialization when a recognized hash implementation is unavailable, then misuses the digest API. Exposure requires an application to verify attacker-controlled PKCS7 signed or signedAndEnveloped data through SMIME or time-stamp APIs; OpenSSL TLS does not reach this path.
Summary
What happened
NULL pointer dereference in PKCS7 verification in OpenSSL 3.0.0 through 3.0.7 allows attackers to crash consuming applications. The signature-verification path fails to check unsuccessful digest initialization when a recognized hash implementation is unavailable, then misuses the digest API. Exposure requires an application to verify attacker-controlled PKCS7 signed or signedAndEnveloped data through SMIME or time-stamp APIs; OpenSSL TLS does not reach this path.
The record
- CVE
- CVE-2023-0401
- Published
- Feb 8, 2023
- Updated
- Nov 4, 2025
- Vendor
- OpenSSL Project
- Product
- OpenSSL
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 8, 2023CVE publishedPublication date reported by the CVE source.
- Nov 4, 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=3.0.0 <3.0.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
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