CVE-2022-4304: Timing Oracle in RSA Decryption
A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE.
For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection.
Other sources
A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a ciphertext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE.
— Red Hat
A timing-based side channel exists in the OpenSSL RSA Decryption implementation, which could be sufficient to recover a ciphertext across a network in a Bleichenbacher style attack. To achieve a successful decryption, an attacker would have to be able to send a very large number of trial messages for decryption. This issue affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP, and RSASVE.
OpenSSL could allow a remote attacker to obtain sensitive information, caused by a timing-based side channel in the RSA Decryption implementation. By sending an overly large number of trial messages for decryption, an attacker could exploit this vulnerability to obtain sensitive information.
— IBM
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
redhat/jbcs-httpd24-opensslto a version that resolves this vulnerability.Fixed in 1:1.1.1k-14.el8 - Upgrade
Upgrade
redhat/jbcs-httpd24-opensslto a version that resolves this vulnerability.Fixed in 1:1.1.1k-14.el7 - Upgrade
Upgrade
redhat/edk2to a version that resolves this vulnerability.Fixed in 0:20220126gitbb1bba3d77-4.el8 - Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 1:1.1.1k-9.el8_7 - Upgrade
Upgrade
redhat/edk2to a version that resolves this vulnerability.Fixed in 0:20220126gitbb1bba3d77-2.el8_6.1 - Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 1:1.1.1k-9.el8_6 - Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 1:3.0.1-47.el9_1 - Upgrade
Upgrade
redhat/edk2to a version that resolves this vulnerability.Fixed in 0:20221207gitfff6d81270b5-9.el9_2 - Upgrade
Upgrade
redhat/opensslto a version that resolves this vulnerability.Fixed in 1:3.0.1-46.el9_0 - Upgrade
Upgrade
redhat/jws5-tomcat-nativeto a version that resolves this vulnerability.Fixed in 0:1.2.31-14.redhat_14.el7 - Upgrade
Upgrade
redhat/jws5-tomcat-nativeto a version that resolves this vulnerability.Fixed in 0:1.2.31-14.redhat_14.el8 - Upgrade
Upgrade
redhat/jws5-tomcat-nativeto a version that resolves this vulnerability.Fixed in 0:1.2.31-14.redhat_14.el9 - Upgrade
Upgrade
rust/openssl-srcto a version that resolves this vulnerability.Fixed in 300.0.12 - Upgrade
Upgrade
rust/openssl-srcto a version that resolves this vulnerability.Fixed in 111.25.0 - Upgrade
Upgrade
debian/opensslto a version that resolves this vulnerability.Fixed in 1.1.1w-0+deb11u1Fixed in 1.1.1n-0+deb11u5Fixed in 3.0.14-1~deb12u1Fixed in 3.0.14-1~deb12u2Fixed in 3.3.2-1 - Upgrade
Upgrade
F5 BIG-IP and BIG-IQ Centralized Managementto a version that resolves this vulnerability.Fixed in 17.1.117.1.0.1 - Upgrade
Upgrade
F5 BIG-IP and BIG-IQ Centralized Managementto a version that resolves this vulnerability.Fixed in 16.1.5 - Upgrade
Upgrade
F5 BIG-IP and BIG-IQ Centralized Managementto a version that resolves this vulnerability.Fixed in 15.1.10 - Upgrade
Upgrade
F5 BIG-IP Nextto a version that resolves this vulnerability.Fixed in 1.8.0 - Upgrade
Upgrade
F5 BIG-IP Nextto a version that resolves this vulnerability.Fixed in 1.2.0
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is CVE-2022-4304?
CVE-2022-4304 is a vulnerability in the OpenSSL RSA Decryption implementation that allows an attacker to recover plaintext data in a Bleichenbacher style attack.
What is the severity of CVE-2022-4304?
The severity of CVE-2022-4304 is medium with a CVSS score of 5.9.
Which software versions are affected by CVE-2022-4304?
OpenSSL versions 1.0.2 to 1.0.2zg, 1.1.1 to 1.1.1t, and 3.0.0 to 3.0.8 are affected by CVE-2022-4304.
How can an attacker exploit CVE-2022-4304?
An attacker can exploit CVE-2022-4304 by sending a large number of trial messages to perform a timing-based side channel attack.
Is there a patch available for CVE-2022-4304?
Yes, patches are available for the affected versions of OpenSSL.