TLS identity forgery via invalid certificate chain
Published Jan 15, 2021 · Updated Aug 4, 2024
Improper certificate validation in Erlang/OTP before 23.2.2 allows remote attackers to accept forged TLS identities via invalid X.509 chains. The ssl application 10.2 builds trust from a malformed certificate chain that reaches a trusted root without enforcing a valid chain relationship. A man-in-the-middle attacker can present the crafted chain during TLS authentication and impersonate a trusted endpoint, subject to a vulnerable peer using this SSL implementation.
Summary
What happened
Improper certificate validation in Erlang/OTP before 23.2.2 allows remote attackers to accept forged TLS identities via invalid X.509 chains. The ssl application 10.2 builds trust from a malformed certificate chain that reaches a trusted root without enforcing a valid chain relationship. A man-in-the-middle attacker can present the crafted chain during TLS authentication and impersonate a trusted endpoint, subject to a vulnerable peer using this SSL implementation.
The record
- CVE
- CVE-2020-35733
- Published
- Jan 15, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 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.
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