TLS peer impersonation via ignored verification failures
Published Dec 12, 2023 · Updated Aug 7, 2024
Improper certificate validation in JRuby jruby-openssl before 0.6 allows remote attackers to impersonate TLS peers with invalid certificates. In OpenSSL::SSL::VERIFY_PEER mode, failed peer-certificate verification silently returns without rejecting the SSL socket. Exposure requires an affected client or client-certificate-validating server, enabling rogue servers or dummy client certificates to be trusted.
Summary
What happened
Improper certificate validation in JRuby jruby-openssl before 0.6 allows remote attackers to impersonate TLS peers with invalid certificates. In OpenSSL::SSL::VERIFY_PEER mode, failed peer-certificate verification silently returns without rejecting the SSL socket. Exposure requires an affected client or client-certificate-validating server, enabling rogue servers or dummy client certificates to be trusted.
The record
- CVE
- CVE-2009-4123
- Published
- Dec 12, 2023
- Updated
- Aug 7, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 12, 2023CVE publishedPublication date reported by the CVE source.
- Aug 7, 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.
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.
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