CVE-2019-1551: rsaz_512_sqr overflow bug on x86_64
An integer overflow was found in the x6464 Montgomery squaring procedure used in exponentiation with 512-bit moduli. As per upstream: No EC algorithms are affected. Attacks against 2-prime RSA1024, 3-prime RSA1536, and DSA1024 as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH512 are considered just feasible. However, for an attack the target would have to re-use the DH512 private key, which is not recommended anyway. Also applications directly using the low level API BNmodexp may be affected if they use BNFLGCONSTTIME
Other sources
As per openssl upstream advisory:
There is an overflow bug in the x6464 Montgomery squaring procedure used in exponentiation with 512-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against 2-prime RSA1024, 3-prime RSA1536, and DSA1024 as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH512 are considered just feasible. However, for an attack the target would have to re-use the DH512 private key, which is not recommended anyway. Also applications directly using the low level API BNmodexp may be affected if they use BNFLGCONSTTIME.
OpenSSL versions 1.1.1 and 1.0.2 are affected by this issue. However due to the low severity of this issue we are not creating new releases at this time. The 1.1.1 mitigation for this issue can be found in commit 419102400. The 1.0.2 mitigation for this issue can be found in commit f1c5eea8a.
— Red Hat
OpenSSL could allow a remote attacker to obtain sensitive information, caused by an overflow in the x6464 Montgomery squaring procedure used in exponentiation with 512-bit moduli. By performing a man-in-the-middle attack, a remote attacker could exploit this vulnerability to obtain sensitive information.
— IBM
There is an overflow bug in the x6464 Montgomery squaring procedure used in exponentiation with 512-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against 2-prime RSA1024, 3-prime RSA1536, and DSA1024 as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH512 are considered just feasible. However, for an attack the target would have to re-use the DH512 private key, which is not recommended anyway. Also applications directly using the low level API BNmodexp may be affected if they use BNFLGCONSTTIME. Fixed in OpenSSL 1.1.1e (Affected 1.1.1-1.1.1d). Fixed in OpenSSL 1.0.2u (Affected 1.0.2-1.0.2t).
Affected Software
Remediation
Information
Patch Available
Patch Available
Patch Available
Event History
Parent advisories
This vulnerability appears in the following advisories.
Frequently Asked Questions
What is the severity of CVE-2019-1551?
CVE-2019-1551 has a high severity rating due to the potential for critical integer overflows in cryptographic operations.
How do I fix CVE-2019-1551?
To fix CVE-2019-1551, update to the appropriate patched versions of the affected packages listed in the vulnerability details.
What software is affected by CVE-2019-1551?
CVE-2019-1551 affects several packages including jbcs-httpd24-apr, jbcs-httpd24-apr-util, and jbcs-httpd24-openssl across various Red Hat versions.
What types of attacks are possible due to CVE-2019-1551?
Although attacks exploiting CVE-2019-1551 are difficult, it can potentially facilitate attacks on RSA and DSA cryptography.
How can I determine if my systems are vulnerable to CVE-2019-1551?
Check the version of OpenSSL and associated packages on your systems against the versions listed as vulnerable in CVE-2019-1551.