CVE-2017-7526
What it is
libgcrypt before version 1.7.8 is vulnerable to a cache side-channel attack resulting into a complete break of RSA-1024 while using the left-to-right method for computing the sliding-window expansion. The same attack is believed to work on RSA-2048 with moderately more computation. This side-channel requires that attacker can run arbitrary software on the hardware where the private RSA key is used.
At a glance
- Exploitability
- Can be exploited over the network without logging in, but needs a user to act. High risk of data exposure.
- Exploit odds
- 3.8% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 3.8% in the next 30 days (EPSS).
- Severity: 6.1 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 3.8% · EPSS, next 30 days
- Weakness
- CWE-200 · Information exposure
- Record status
- Modified
Affected
- Gnupg Libgcrypt < 1.7.8
- Canonical Ubuntu Linux 12.04
- Canonical Ubuntu Linux 14.04
- Canonical Ubuntu Linux 16.04
- Debian Linux 8.0
- Debian Linux 9.0
Attack profile CVSS 3.0 · 6.1
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Raw vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2017-7526.md and follow it. Check whether this project is affected by CVE-2017-7526. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-7526
- https://lists.gnupg.org/pipermail/gnupg-announce/2017q2/000408.html
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-7526
- https://lists.gnupg.org/pipermail/gnupg-announce/2017q2/000408.html
References
- http://www.securityfocus.com/bid/99338
- http://www.securitytracker.com/id/1038915
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-7526
- https://eprint.iacr.org/2017/627
- https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git%3Ba=commit%3Bh=78130828e9a140a9de4dafadbc844dbb64cb709a
- https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git%3Ba=commit%3Bh=8725c99ffa41778f382ca97233183bcd687bb0ce
- https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git%3Ba=commit%3Bh=e6a3dc9900433bbc8ad362a595a3837318c28fa9
- https://lists.gnupg.org/pipermail/gnupg-announce/2017q2/000408.html
- https://usn.ubuntu.com/3733-1/
- https://usn.ubuntu.com/3733-2/
- https://www.debian.org/security/2017/dsa-3901
- https://www.debian.org/security/2017/dsa-3960
- http://www.securityfocus.com/bid/99338
- http://www.securitytracker.com/id/1038915
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-7526
- https://eprint.iacr.org/2017/627
- https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git%3Ba=commit%3Bh=78130828e9a140a9de4dafadbc844dbb64cb709a
- https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git%3Ba=commit%3Bh=8725c99ffa41778f382ca97233183bcd687bb0ce
- https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git%3Ba=commit%3Bh=e6a3dc9900433bbc8ad362a595a3837318c28fa9
- https://lists.gnupg.org/pipermail/gnupg-announce/2017q2/000408.html
- https://usn.ubuntu.com/3733-1/
- https://usn.ubuntu.com/3733-2/
- https://www.debian.org/security/2017/dsa-3901
- https://www.debian.org/security/2017/dsa-3960