The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before…
No fixed version listed yet.Check the vendor advisory. References ↓
The ssl3_get_key_exchange function in s3_clnt.c within OpenSSL, in the 0.9.8, 1.0.0 and 1.0.1 release lines before their fixed versions, is a flaw in client-side SSL/TLS handling. A remote SSL server can exploit it by offering a weak ephemeral RSA key in a noncompliant role, forcing an RSA-to-EXPORT_RSA downgrade that facilitates brute-force decryption; the issue applies only to OpenSSL-based clients, not to servers or other TLS implementations.
Official description · CVE.org
The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k allows remote SSL servers to conduct RSA-to-EXPORT_RSA downgrade attacks and facilitate brute-force decryption by offering a weak ephemeral RSA key in a noncompliant role, related to the "FREAK" issue. NOTE: the scope of this CVE is only client code based on OpenSSL, not EXPORT_RSA issues associated with servers or other TLS implementations.
- Exploited
- Yes, in VulnCheck KEV
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 16 months after disclosure. Public exploit code (PoC-in-GitHub) appeared 54 days after disclosure.
- Disclosedday 0
- Public exploit codePoC-in-GitHub+54 days
- First seen exploitedVulnCheck KEV evidence+16 mo
Patch historyEarlier and later CVEs in the same code, in date order. It shows when a fix was bypassed or incomplete and which version finally fixed it.
See the family tree8 related vulnerabilities in the same code over 9 years.
Same bug familyLinked by evidence that a fix failed or the same code was patched again. Oldest first.
relatedMedium
Why these are linked: Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
- Same code patched: s3_clnt.c (machine-matched)Functions: ssl3_get_key_exchangecommit b15f876commit ce325c6
This CVECVE-2015-0204The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL…9 Jan 2015relatedMedium
Why these are linked: Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
- Same code patched: s3_srvr.c (machine-matched)commit ce325c6commit 1421e0c
- same family
relatedMedium
Why these are linked: Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
- Same code patched: ssl_locl.h (machine-matched)commit 98ece4ecommit 4ad9361
- same family
- same family
relatedMedium
Why these are linked: Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
- Same code patched: ssl_lib.c (machine-matched)commit e9d7083commit 7e4d731commit e86ac43commit 99fb785
What security researchers reported
Not named in any threat report yetAlso mentioned in 2 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- Proof Point Emerging Exploit list14 Dec 2022
- Internal CVE Research9 Mar 2022