Certificate verification bypass via premature TLS session caching
Published Jun 8, 2020 · Updated Aug 4, 2024
Certificate validation in Node.js 12.x before 12.18.0 and 14.x before 14.4.0 allows man-in-the-middle attackers to bypass TLS hostname checks. The TLS layer emits the session event before secureConnect, allowing an unauthorized connection's session ticket to be cached and reused as authorized. Exploitation requires an application that saves or automatically caches TLS sessions, including the built-in HTTPS agent, and permits interception of the initial connection.
Summary
What happened
Certificate validation in Node.js 12.x before 12.18.0 and 14.x before 14.4.0 allows man-in-the-middle attackers to bypass TLS hostname checks. The TLS layer emits the session event before secureConnect, allowing an unauthorized connection's session ticket to be cached and reused as authorized. Exploitation requires an application that saves or automatically caches TLS sessions, including the built-in HTTPS agent, and permits interception of the initial connection.
The record
- CVE
- CVE-2020-8172
- Published
- Jun 8, 2020
- Updated
- Aug 4, 2024
- Vendor
- Node.js
- Product
- Node.js
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 8, 2020CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=12.18.0,14.4.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.
Public exploit references
- HackerOne report 811502proof of concept · unverified
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