First published: Fri Dec 06 2019(Updated: )
An integer overflow was found in the x64_64 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 BN_mod_exp may be affected if they use BN_FLG_CONSTTIME
Credit: openssl-security@openssl.org openssl-security@openssl.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/jbcs-httpd24-apr | <0:1.6.3-104.jbcs.el6 | 0:1.6.3-104.jbcs.el6 |
redhat/jbcs-httpd24-apr-util | <0:1.6.1-75.jbcs.el6 | 0:1.6.1-75.jbcs.el6 |
redhat/jbcs-httpd24-brotli | <0:1.0.6-38.jbcs.el6 | 0:1.0.6-38.jbcs.el6 |
redhat/jbcs-httpd24-curl | <0:7.64.1-44.jbcs.el6 | 0:7.64.1-44.jbcs.el6 |
redhat/jbcs-httpd24-httpd | <0:2.4.37-64.jbcs.el6 | 0:2.4.37-64.jbcs.el6 |
redhat/jbcs-httpd24-jansson | <0:2.11-53.jbcs.el6 | 0:2.11-53.jbcs.el6 |
redhat/jbcs-httpd24-nghttp2 | <0:1.39.2-34.jbcs.el6 | 0:1.39.2-34.jbcs.el6 |
redhat/jbcs-httpd24-openssl | <1:1.1.1c-32.jbcs.el6 | 1:1.1.1c-32.jbcs.el6 |
redhat/jbcs-httpd24-apr | <0:1.6.3-104.jbcs.el7 | 0:1.6.3-104.jbcs.el7 |
redhat/jbcs-httpd24-apr-util | <0:1.6.1-75.jbcs.el7 | 0:1.6.1-75.jbcs.el7 |
redhat/jbcs-httpd24-brotli | <0:1.0.6-38.jbcs.el7 | 0:1.0.6-38.jbcs.el7 |
redhat/jbcs-httpd24-curl | <0:7.64.1-44.jbcs.el7 | 0:7.64.1-44.jbcs.el7 |
redhat/jbcs-httpd24-httpd | <0:2.4.37-64.jbcs.el7 | 0:2.4.37-64.jbcs.el7 |
redhat/jbcs-httpd24-jansson | <0:2.11-53.jbcs.el7 | 0:2.11-53.jbcs.el7 |
redhat/jbcs-httpd24-nghttp2 | <0:1.39.2-34.jbcs.el7 | 0:1.39.2-34.jbcs.el7 |
redhat/jbcs-httpd24-openssl | <1:1.1.1c-32.jbcs.el7 | 1:1.1.1c-32.jbcs.el7 |
redhat/jbcs-httpd24-openssl-chil | <0:1.0.0-1.jbcs.el7 | 0:1.0.0-1.jbcs.el7 |
redhat/openssl | <1:1.1.1g-11.el8 | 1:1.1.1g-11.el8 |
debian/openssl | <=1.1.1d-0+deb10u4<=1.1.1d-2 | 1.1.1d-0+deb10u5 1.1.1e-1 |
redhat/openssl | <1.1.1 | 1.1.1 |
OpenSSL OpenSSL | >=1.0.2<=1.0.2t | |
OpenSSL OpenSSL | >=1.1.1<=1.1.1d | |
openSUSE Leap | =15.1 | |
Oracle Enterprise Manager Ops Center | =12.4.0.0 | |
Oracle Mysql Enterprise Monitor | <=4.0.12 | |
Oracle Mysql Enterprise Monitor | >=8.0.0<=8.0.20 | |
Oracle PeopleSoft Enterprise PeopleTools | =8.56 | |
Oracle PeopleSoft Enterprise PeopleTools | =8.57 | |
Oracle PeopleSoft Enterprise PeopleTools | =8.58 | |
Canonical Ubuntu Linux | =16.04 | |
Canonical Ubuntu Linux | =18.04 | |
Canonical Ubuntu Linux | =19.10 | |
Fedoraproject Fedora | =30 | |
Fedoraproject Fedora | =31 | |
Fedoraproject Fedora | =32 | |
Debian Debian Linux | =9.0 | |
Debian Debian Linux | =10.0 | |
Tenable Log Correlation Engine | <6.0.9 | |
IBM Security Verify Governance | <=10.0 | |
debian/openssl | 1.1.1w-0+deb11u1 1.1.1w-0+deb11u2 3.0.15-1~deb12u1 3.0.14-1~deb12u2 3.3.2-2 |
For Red Hat Enterprise Linux 7, 512 bit DH is already disabled. As this bug is about leakage of the private key to the attacker, it should be fully sufficient to just not use 1024 bit RSA keys or 1024 bit DSA keys. These keys are not secure enough anyway. 3-prime RSA keys are not supported on RHEL-7. For Red Hat Enterprise 8, The DEFAULT crypto policy already disables all these key sizes. Also applications compiled with openssl which use the low level API BN_mod_exp may be affected if they use BN_FLG_CONSTTIME, other users of this API are not affected by this flaw.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)