Certificate revocation bypass via unauthorized OCSP signer
Published Nov 27, 2022 · Updated Apr 25, 2025
Improper certificate validation in Botan 1.11.34 through 2.19.2 allows man-in-the-middle attackers to forge OCSP revocation status. OCSP response validation accepts any valid signature from an embedded responder certificate without verifying that the issuing CA authorized that responder. An attacker able to spoof or staple a response can mark legitimate certificates revoked or present a revoked certificate as valid, enabling TLS server impersonation when applications rely on OCSP.
Summary
What happened
Improper certificate validation in Botan 1.11.34 through 2.19.2 allows man-in-the-middle attackers to forge OCSP revocation status. OCSP response validation accepts any valid signature from an embedded responder certificate without verifying that the issuing CA authorized that responder. An attacker able to spoof or staple a response can mark legitimate certificates revoked or present a revoked certificate as valid, enabling TLS server impersonation when applications rely on OCSP.
The record
- CVE
- CVE-2022-43705
- Published
- Nov 27, 2022
- Updated
- Apr 25, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 27, 2022CVE publishedPublication date reported by the CVE source.
- Apr 25, 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
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