medium
6.8
CWE
190
Advisory Published
Updated

CVE-2019-1551: rsaz_512_sqr overflow bug on x86_64

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

Affected SoftwareAffected VersionHow 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
IBM Security Verify Governance<=10.0
OpenSSL libcrypto>=1.0.2<=1.0.2t
OpenSSL libcrypto>=1.1.1<=1.1.1d
openSUSE=15.1
Oracle Enterprise Manager Ops Center=12.4.0.0
MySQL Enterprise Monitor<=4.0.12
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
Ubuntu Linux=16.04
Ubuntu Linux=18.04
Ubuntu Linux=19.10
Fedoraproject Fedora=30
Fedoraproject Fedora=31
Fedoraproject Fedora=32
Debian GNU/Linux=9.0
Debian GNU/Linux=10.0
Tenable Log Correlation Engine<6.0.9
debian/openssl
1.1.1w-0+deb11u1
1.1.1w-0+deb11u2
3.0.15-1~deb12u1
3.0.14-1~deb12u2
3.4.0-2
3.4.1-1
Ubuntu=16.04
Ubuntu=18.04
Ubuntu=19.10
Fedora=30
Fedora=31
Fedora=32
Debian=9.0
Debian=10.0

Remedy

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.

Remedy

https://www.oracle.com/security-alerts/cpuApr2021.html

Remedy

https://www.oracle.com/security-alerts/cpujan2021.html

Remedy

https://www.oracle.com/security-alerts/cpujul2020.html

Remedy

https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=419102400a2811582a7a3d4a4e317d72e5ce0a8f

Remedy

https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=f1c5eea8a817075d31e43f5876993c6710238c98

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Parent vulnerabilities

(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.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203