CVE-2017-9526: Infoleak
First published: Sun Jun 11 2017(Updated: )
In Libgcrypt before 1.7.7, an attacker who learns the EdDSA session key (from side-channel observation during the signing process) can easily recover the long-term secret key. 1.7.7 makes a cipher/ecc-eddsa.c change to store this session key in secure memory, to ensure that constant-time point operations are used in the MPI library.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| debian/libgcrypt20 | 1.8.7-6 1.10.1-3 1.11.0-7 | |
| Libgcrypt | <=1.7.6 |
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.
Reference Links
- http://www.debian.org/security/2017/dsa-3880
- http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html
- http://www.securityfocus.com/bid/99046
- https://bugzilla.suse.com/show_bug.cgi?id=1042326
- https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=5a22de904a0a366ae79f03ff1e13a1232a89e26b
- https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=f9494b3f258e01b6af8bd3941ce436bcc00afc56
- https://www.oracle.com/technetwork/security-advisory/cpujan2019-5072801.html
- https://launchpad.net/bugs/cve/CVE-2017-9526
- https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git%3Ba=commit%3Bh=5a22de904a0a366ae79f03ff1e13a1232a89e26b
- https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git%3Ba=commit%3Bh=f9494b3f258e01b6af8bd3941ce436bcc00afc56
- https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=bc5199a02abe428ad377443280b3eda60141a1d6
- https://security-tracker.debian.org/tracker/CVE-2017-9526
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9526
- https://nvd.nist.gov/vuln/detail/CVE-2017-9526
- https://ubuntu.com/security/CVE-2017-9526
Frequently Asked Questions
What is the impact of CVE-2017-9526?
The impact of CVE-2017-9526 is that an attacker can recover long-term secret keys if they learn the EdDSA session key through side-channel attacks during the signing process.
What versions of Libgcrypt are affected by CVE-2017-9526?
Libgcrypt versions prior to 1.7.7 are affected by CVE-2017-9526.
How can I mitigate CVE-2017-9526?
To mitigate CVE-2017-9526, update Libgcrypt to version 1.8.7-6 or later, or 1.10.1-3 or later, or 1.11.0-7 or later.
What changes were made in Libgcrypt to address CVE-2017-9526?
Libgcrypt 1.7.7 introduced changes to store the EdDSA session key in secure memory to prevent side-channel attacks.
Is exploitation of CVE-2017-9526 easy for attackers?
Yes, exploitation of CVE-2017-9526 is relatively easy for attackers who can monitor the signing process.
- collector/launchpad-cve
- source/Launchpad
- agent/type
- agent/author
- agent/weakness
- agent/severity
- collector/usn-cve
- source/Ubuntu
- agent/references
- agent/remedy
- agent/description
- agent/first-publish-date
- agent/event
- agent/trending
- agent/last-modified-date
- collector/security-tracker-debian
- source/Debian
- agent/software-canonical-lookup
- agent/source
- agent/tags
- agent/softwarecombine
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup-request
- collector/nvd-index
- package-manager/debian
- vendor/gnupg
- canonical/libgcrypt
- version/libgcrypt/1.7.6