Server authentication bypass via cached TLS session
Published Feb 3, 2024 · Updated Jun 20, 2025
Improper certificate revocation checking in curl 8.5.0 allows remote attackers to bypass OCSP verification during TLS session reuse. The OpenSSL backend retains a session ID after verifystatus fails, so a later connection to the same hostname reuses that session and skips the status check. Reachability requires an OpenSSL build, TLS 1.2, OCSP status verification, and a fresh cached session; the client can then accept a server whose revocation check failed.
Summary
What happened
Improper certificate revocation checking in curl 8.5.0 allows remote attackers to bypass OCSP verification during TLS session reuse. The OpenSSL backend retains a session ID after verifystatus fails, so a later connection to the same hostname reuses that session and skips the status check. Reachability requires an OpenSSL build, TLS 1.2, OCSP status verification, and a fresh cached session; the client can then accept a server whose revocation check failed.
The record
- CVE
- CVE-2024-0853
- Published
- Feb 3, 2024
- Updated
- Jun 20, 2025
- Vendor
- curl
- Product
- curl
- Classifications
- CWE-295, CWE-299, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 3, 2024CVE publishedPublication date reported by the CVE source.
- Jun 20, 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=8.5.0 <=8.5.0
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.
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