Certificate verification error misreporting via discarded leaf errors
Published Apr 12, 2023 · Updated Feb 10, 2025
Improper certificate validation in LibreSSL before 3.6.1 and OpenBSD 7.2 before errata 001 allows remote attackers to cause incorrect errors. The x509_verify_ctx_add_chain function clears the context error without copying a continued leaf-certificate failure into cert_errors[0]. An installed verification callback must continue after detecting an invalid certificate, causing callers to receive an unreliable verification result.
Summary
What happened
Improper certificate validation in LibreSSL before 3.6.1 and OpenBSD 7.2 before errata 001 allows remote attackers to cause incorrect errors. The x509_verify_ctx_add_chain function clears the context error without copying a continued leaf-certificate failure into cert_errors[0]. An installed verification callback must continue after detecting an invalid certificate, causing callers to receive an unreliable verification result.
The record
- CVE
- CVE-2022-48437
- Published
- Apr 12, 2023
- Updated
- Feb 10, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-295
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 12, 2023CVE publishedPublication date reported by the CVE source.
- Feb 10, 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.
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