TLS plaintext disclosure via RSA timing oracle
Published Feb 5, 2024 · Updated Mar 24, 2026
Observable timing discrepancy in cryptography before 42.0.0 allows remote attackers to decrypt captured messages from RSA TLS sessions. RSA PKCS#1 v1.5 decryption exposes padding failures through distinguishable Python exception paths instead of backend implicit rejection. Reachability requires an application that exposes RSA PKCS#1 v1.5 decryption, and confidentiality is the only reported impact.
Summary
What happened
Observable timing discrepancy in cryptography before 42.0.0 allows remote attackers to decrypt captured messages from RSA TLS sessions. RSA PKCS#1 v1.5 decryption exposes padding failures through distinguishable Python exception paths instead of backend implicit rejection. Reachability requires an application that exposes RSA PKCS#1 v1.5 decryption, and confidentiality is the only reported impact.
The record
- CVE
- CVE-2023-50782
- Published
- Feb 5, 2024
- Updated
- Mar 24, 2026
- Vendor
- Red Hat
- Product
- Red Hat Enterprise Linux 8
- Classifications
- CWE-203, T1040
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 5, 2024CVE publishedPublication date reported by the CVE source.
- Mar 24, 2026Record 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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.
Public exploit references
- Marvin Toolkit pyca-cryptography timing testproof 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