Server impersonation via missing certificate-key checks
Published Jan 29, 2021 · Updated Aug 3, 2024
Improper certificate validation in wolfSSL before 4.7.0 allows man-in-the-middle attackers to impersonate TLS 1.3 servers. DoTls13CertificateVerify continues after receiving an Ed25519, Ed448, ECC, or RSA signature when no corresponding peer certificate key is present. Only TLS 1.3 client applications are exposed; server-only deployments and clients without TLS 1.3 enabled are unaffected.
Summary
What happened
Improper certificate validation in wolfSSL before 4.7.0 allows man-in-the-middle attackers to impersonate TLS 1.3 servers. DoTls13CertificateVerify continues after receiving an Ed25519, Ed448, ECC, or RSA signature when no corresponding peer certificate key is present. Only TLS 1.3 client applications are exposed; server-only deployments and clients without TLS 1.3 enabled are unaffected.
The record
- CVE
- CVE-2021-3336
- Published
- Jan 29, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 29, 2021CVE 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.
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