GLSA-201612-01 : GnuPG: RNG output is predictable
Medium Nessus Plugin ID 95516
SynopsisThe remote Gentoo host is missing one or more security-related patches.
DescriptionThe remote host is affected by the vulnerability described in GLSA-201612-01 (GnuPG: RNG output is predictable)
A long standing bug (since 1998) in Libgcrypt (see “GLSA 201610-04”
below) and GnuPG allows an attacker to predict the output from the standard RNG. Please review the “Entropy Loss and Output Predictability in the Libgcrypt PRNG” paper below for a deep technical analysis.
An attacker who obtains 580 bytes of the random number from the standard RNG can trivially predict the next 20 bytes of output.
This flaw does not affect the default generation of keys, because running gpg for key creation creates at most 2 keys from the pool. For a single 4096 bit RSA key, 512 bytes of random are required and thus for the second key (encryption subkey), 20 bytes could be predicted from the the first key.
However, the security of an OpenPGP key depends on the primary key (which was generated first) and thus the 20 predictable bytes should not be a problem. For the default key length of 2048 bit nothing will be predictable.
There is no known workaround at this time.
SolutionAll GnuPG 1 users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose '>=app-crypt/gnupg-1.4.21'