- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory                           GLSA 201408-10
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
                                            https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

 Severity: Normal
    Title: Libgcrypt: Side-channel attack
     Date: August 29, 2014
     Bugs: #519396
       ID: 201408-10

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Synopsis
=======
A vulnerability in Libgcrypt could allow a remote attacker to extract
ElGamal private key information.

Background
=========
Libgcrypt is a general purpose cryptographic library derived out of
GnuPG.

Affected packages
================
    -------------------------------------------------------------------
     Package              /     Vulnerable     /            Unaffected
    -------------------------------------------------------------------
  1  dev-libs/libgcrypt           < 1.5.4                    >= 1.5.4

Description
==========
A vulnerability in the implementation of ElGamal decryption procedures
of Libgcrypt leaks information to various side-channels.

Impact
=====
A physical side-channel attack allows a remote attacker to fully
extract decryption keys during the decryption of a chosen ciphertext.

Workaround
=========
There is no known workaround at this time.

Resolution
=========
All Libgcrypt users should upgrade to the latest version:

  # emerge --sync
  # emerge --ask --oneshot --verbose ">=dev-libs/libgcrypt-1.5.4"

References
=========
[ 1 ] CVE-2014-5270
      http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-5270

Availability
===========
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:

 https://security.gentoo.org/glsa/201408-10

Concerns?
========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.

License
======
Copyright 2014 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).

The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.

https://creativecommons.org/licenses/by-sa/2.5/

Gentoo: GLSA-201408-10: Libgcrypt: Side-channel attack

A vulnerability in Libgcrypt could allow a remote attacker to extract ElGamal private key information.

Summary

A vulnerability in the implementation of ElGamal decryption procedures of Libgcrypt leaks information to various side-channels.

Resolution

All Libgcrypt users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=dev-libs/libgcrypt-1.5.4"

References

[ 1 ] CVE-2014-5270 http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-5270

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/201408-10

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity
Severity: Normal
Title: Libgcrypt: Side-channel attack
Date: August 29, 2014
Bugs: #519396
ID: 201408-10

Synopsis

A vulnerability in Libgcrypt could allow a remote attacker to extract ElGamal private key information.

Background

Libgcrypt is a general purpose cryptographic library derived out of GnuPG.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-libs/libgcrypt < 1.5.4 >= 1.5.4

Impact

===== A physical side-channel attack allows a remote attacker to fully extract decryption keys during the decryption of a chosen ciphertext.

Workaround

There is no known workaround at this time.

Related News