Authentication bypass via omitted CertificateVerify message
Published Feb 24, 2022 · Updated Aug 3, 2024
Authentication bypass in wolfSSL before 5.2.0 allows remote attackers to complete a TLS 1.3 mutual-authentication handshake without a certificate. DoTls13Finished accepted the client's Finished message without requiring both havePeerCert and havePeerVerify when mutual authentication was configured. A reachable TLS 1.3 server must require client certificates; omitting CertificateVerify then grants access as an authenticated client.
Summary
What happened
Authentication bypass in wolfSSL before 5.2.0 allows remote attackers to complete a TLS 1.3 mutual-authentication handshake without a certificate. DoTls13Finished accepted the client's Finished message without requiring both havePeerCert and havePeerVerify when mutual authentication was configured. A reachable TLS 1.3 server must require client certificates; omitting CertificateVerify then grants access as an authenticated client.
The record
- CVE
- CVE-2022-25640
- Published
- Feb 24, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-295
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 24, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record 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