First published: Thu Jul 26 2018(Updated: )
Last updated 24 July 2024
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Libgcrypt | <1.7.8 | |
Ubuntu | =12.04 | |
Ubuntu | =14.04 | |
Ubuntu | =16.04 | |
Debian Linux | =8.0 | |
Debian Linux | =9.0 | |
debian/gnupg1 | 1.4.23-1.1 1.4.23-3 | |
debian/gnupg2 | 2.2.27-2+deb11u2 2.2.40-1.1 2.2.46-6 2.4.7-14 | |
debian/libgcrypt20 | 1.8.7-6 1.10.1-3 1.11.0-7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-7526 has been classified as a high severity vulnerability due to its potential to allow complete breakage of RSA-1024 and RSA-2048 implementations.
To mitigate CVE-2017-7526, upgrade to libgcrypt version 1.7.8 or later along with relevant updates to affected software packages.
CVE-2017-7526 affects libgcrypt versions before 1.7.8, as well as specific versions of gnupg1 and gnupg2 on Debian and Ubuntu distributions.
CVE-2017-7526 allows attackers to exploit cache side-channel vulnerabilities that can completely break RSA encryption implementations using affected versions.
CVE-2017-7526 was disclosed on July 24, 2024, although the vulnerability itself has existed in libgcrypt versions prior to 1.7.8.