Red Hat Bugzilla – Bug 1128531
CVE-2014-5270 libgcrypt: ELGAMAL side-channel attack
Last modified: 2016-05-22 21:05:11 EDT
It was reported that libgcrypt was vulnerable to an ELGAMAL side-channel attack: https://lists.fedoraproject.org/pipermail/security-team/2014-August/000055.html http://lists.gnupg.org/pipermail/gnupg-announce/2014q3/000352.html In the above reports, this issue presented when using GnuPG with a version of libgcrypt older than 1.6.0 or older than 1.5.4. Similar to CVE-2013-4242/bug 988589, this could possibly be used to obtain the majority of a private key from memory. References: http://www.cs.unc.edu/~reiter/papers/2012/CCS.pdf
Created mingw32-libgcrypt tracking bugs for this issue: Affects: epel-5 [bug 1128532]
Created mingw-libgcrypt tracking bugs for this issue: Affects: fedora-all [bug 1128533]
CVE request: http://www.openwall.com/lists/oss-security/2014/08/11/1
Has a CVE meanwhile be assigned? Can't you get one from the Redhat pool?
MITRE assigned CVE-2014-5270 to the "touching exposed metal on the computer's chassis". Further details: http://seclists.org/oss-sec/2014/q3/383
Statement: This issue affects the versions of libgcrypt as shipped with Red Hat Enterprise Linux 6 and 7. A future update may address this issue. This issue affects the version of gnupg and libgcrypt as shipped with Red Hat Enterprise Linux 5. Red Hat Enterprise Linux 5 is now in Production 3 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.
This issue was fixed in libgcrypt-1.5.x via the following commits: http://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=62e8e1283268f1d3b6d0cfb2fc4e7835bbcdaab6 http://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commitdiff;h=5958574a8285e9d759d7d95418cacd3d352f77a2 libgcrypt-1.5.4 was released to address this issue. This issue was fixed in gnupg-1.x via the following commits: http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=cad8216f9a0b33c9dc84ecc4f385b00045e7b496 gnupg-1.4.16 was released to address this issue.