Client crash via unchecked certificate-key type cast
Published Jul 15, 2021 · Updated Aug 4, 2024
Improper certificate validation in Go crypto/tls before 1.15.14 and 1.16.0 through 1.16.5 allows attackers to crash TLS clients. rsaKeyAgreement.generateClientKeyExchange assumes the certificate public key is RSA and performs an unchecked type assertion when TLS_RSA is negotiated, so an ECDSA or Ed25519 key triggers a panic. Exploitation requires a privileged network position plus a trusted non-RSA server certificate, or a client using Config.InsecureSkipVerify; TLS 1.3-only clients are unaffected.
Summary
What happened
Improper certificate validation in Go crypto/tls before 1.15.14 and 1.16.0 through 1.16.5 allows attackers to crash TLS clients. rsaKeyAgreement.generateClientKeyExchange assumes the certificate public key is RSA and performs an unchecked type assertion when TLS_RSA is negotiated, so an ECDSA or Ed25519 key triggers a panic. Exploitation requires a privileged network position plus a trusted non-RSA server certificate, or a client using Config.InsecureSkipVerify; TLS 1.3-only clients are unaffected.
The record
- CVE
- CVE-2021-34558
- Published
- Jul 15, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-295, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 15, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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