TLS client-authentication bypass via omitted CertificateVerify
Published Jan 15, 2020 · Updated Sep 30, 2024
Authentication bypass in Oracle Java SE 11.0.5 and 13.0.1 JSSE allows remote attackers to access TLS-protected application data. The JSSE server state machine completes a TLS handshake when a client omits CertificateVerify, so required certificate possession is never proven. Exploitation requires an application that uses affected JSSE APIs for TLS client authentication; success permits unauthenticated reading or modification of application data.
Summary
What happened
Authentication bypass in Oracle Java SE 11.0.5 and 13.0.1 JSSE allows remote attackers to access TLS-protected application data. The JSSE server state machine completes a TLS handshake when a client omits CertificateVerify, so required certificate possession is never proven. Exploitation requires an application that uses affected JSSE APIs for TLS client authentication; success permits unauthenticated reading or modification of application data.
The record
- CVE
- CVE-2020-2655
- Published
- Jan 15, 2020
- Updated
- Sep 30, 2024
- Vendor
- Oracle Corporation
- Product
- Java Platform, Standard Edition (Java SE)
- Classifications
- CWE-841, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 15, 2020CVE publishedPublication date reported by the CVE source.
- Sep 30, 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=Java SE: 11.0.5, 13.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- JSSE client-authentication bypass handshake sequenceproof of concept · demonstrated
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