A vulnerability has been discovered in GnuPG, which can lead to arbitrary code execution.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| app-crypt/gnupg | * | < 2.5.14 | >= 2.5.14 |
The GNU Privacy Guard, GnuPG, is a free replacement for the PGP suite of cryptographic software.
A vulnerability has been discovered in GnuPG's armor parser.
A remote attacker could entice a user or automated system to process a specially crafted signature file, possibly resulting in execution of arbitrary commands with the privileges of the process.
There is no known workaround at this time.
All GnuPG users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=app-crypt/gnupg-2.5.14"
Multiple vulnerabilities have been discovered in GnuPG, the worst of which could lead to signature spoofing.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| app-crypt/gnupg | * | < 2.4.4 | >= 2.4.4 |
The GNU Privacy Guard, GnuPG, is a free replacement for the PGP suite of cryptographic software.
Multiple vulnerabilities have been discovered in GnuPG. Please review the CVE identifiers referenced below for details.
Please review the referenced CVE identifiers for details.
There is no known workaround at this time.
All GnuPG users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=app-crypt/gnupg-2.4.4"
Due to a design flaw, the output of GnuPG's Random Number Generator (RNG) is predictable.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| app-crypt/gnupg | * | < 1.4.21 | >= 1.4.21 |
The GNU Privacy Guard, GnuPG, is a free replacement for the PGP suite of cryptographic software.
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.
All GnuPG 1 users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=app-crypt/gnupg-1.4.21"
Multiple vulnerabilities have been found in GnuPG and libgcrypt, the worst of which may allow a local attacker to obtain confidential key information.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| app-crypt/gnupg | * | < 2.0.26-r3 | >= 2.0.26-r3, >= 1.4.19 (revision), >= 1.4.20 (revision), >= 1.4.21 (revision), >= 1.4.22 (revision) |
| dev-libs/libgcrypt | * | < 1.6.3-r4 | >= 1.6.3-r4 |
The GNU Privacy Guard, GnuPG, is a free replacement for the PGP suite of cryptographic software.
Multiple vulnerabilities have been discovered in GnuPG and libgcrypt, please review the CVE identifiers referenced below for details.
A local attacker could possibly cause a Denial of Service condition. Side-channel attacks could be leveraged to obtain key material.
There is no known workaround at this time.
All GnuPG 2 users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=app-crypt/gnupg-2.0.26-r3"
All GnuPG 1 users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=app-crypt/gnupg-1.4.19"
All libgcrypt users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=dev-libs/libgcrypt-1.6.3-r4"
A vulnerability in GnuPG can lead to a Denial of Service condition.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| app-crypt/gnupg | * | < 2.0.24 | >= 2.0.24, >= 1.4.17 (revision), >= 1.4.18 (revision), >= 1.4.19 (revision), >= 1.4.20 (revision), >= 1.4.21 (revision) |
The GNU Privacy Guard, GnuPG, is a free replacement for the PGP suite of cryptographic software.
GnuPG does not properly handle a specially crated compressed packet resulting in an infinite loop.
A context-dependent attacker can cause a Denial of Service.
There is no known workaround at this time.
All GnuPG 2.0 users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=app-crypt/gnupg-2.0.24"
All GnuPG 1.4 users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=app-crypt/gnupg-1.4.17"
Multiple vulnerabilities have been discovered in GnuPG and Libgcrypt, which may result in execution of arbitrary code, Denial of Service, or the disclosure of private keys.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| app-crypt/gnupg | * | < 2.0.22 | >= 2.0.22, >= 1.4.16 (revision), >= 1.4.17 (revision), >= 1.4.18 (revision), >= 1.4.19 (revision), >= 1.4.20 (revision), >= 1.4.21 (revision) |
| dev-libs/libgcrypt | * | < 1.5.3 | >= 1.5.3 |
The GNU Privacy Guard, GnuPG, is a free replacement for the PGP suite of cryptographic software. Libgcrypt is a cryptographic library based on GnuPG.
Multiple vulnerabilities have been discovered in GnuPG and Libgcrypt. Please review the CVE identifiers referenced below for details.
An unauthenticated remote attacker may be able to execute arbitrary code with the privileges of the user running GnuPG, cause a Denial of Service condition, or bypass security restrictions. Additionally, a side-channel attack may allow a local attacker to recover a private key, please review “Flush+Reload: a High Resolution, Low Noise, L3 Cache Side-Channel Attack” in the References section for further details.
There is no known workaround at this time.
All GnuPG 2.0 users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=app-crypt/gnupg-2.0.22"
All GnuPG 1.4 users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=app-crypt/gnupg-1.4.16"
All Libgcrypt users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=dev-libs/libgcrypt-1.5.3"
The GPGSM utility included in GnuPG contains a use-after-free vulnerability that may allow an unauthenticated remote attacker to execute arbitrary code.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| app-crypt/gnupg | * | < 2.0.16-r1 | >= 2.0.16-r1, < 2.0 |
The GNU Privacy Guard, GnuPG, is a free replacement for the PGP suite of cryptographic software. The GPGSM utility in GnuPG is responsible for processing X.509 certificates, signatures and encryption as well as S/MIME messages.
The GPGSM utility in GnuPG contains a use-after-free vulnerability that may be exploited when importing a crafted X.509 certificate explicitly or during the signature verification process.
An unauthenticated remote attacker may execute arbitrary code with the privileges of the user running GnuPG by enticing them to import a crafted certificate.
There is no known workaround at this time.
All GnuPG 2.x users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=app-crypt/gnupg-2.0.16-r1"
GnuPG is vulnerable to a buffer overflow and an erroneous function pointer dereference that can result in the execution of arbitrary code.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| app-crypt/gnupg | * | < 1.4.6 | >= 1.4.6 |
The GNU Privacy Guard, GnuPG, is a free replacement for the PGP suite of cryptographic software.
Hugh Warrington has reported a boundary error in GnuPG, in the "ask_outfile_name()" function from openfile.c: the make_printable_string() function could return a string longer than expected. Additionally, Tavis Ormandy of the Gentoo Security Team reported a design error in which a function pointer can be incorrectly dereferenced.
A remote attacker could entice a user to interactively use GnuPG on a crafted file and trigger the boundary error, which will result in a buffer overflow. They could also entice a user to process a signed or encrypted file with gpg or gpgv, possibly called through another application like a mail client, to trigger the dereference error. Both of these vulnerabilities would result in the execution of arbitrary code with the permissions of the user running GnuPG. gpg-agent, gpgsm and other tools are not affected.
There is no known workaround at this time.
All GnuPG users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose "=app-crypt/gnupg-1.4*"
GnuPG is vulnerable to an integer overflow that could lead to the execution of arbitrary code.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| app-crypt/gnupg | * | < 1.4.5 | >= 1.4.5 |
The GNU Privacy Guard, GnuPG, is a free replacement for the PGP suite of cryptographic software.
Evgeny Legerov discovered a vulnerability in GnuPG that when certain packets are handled an integer overflow may occur.
By sending a specially crafted email to a user running an affected version of GnuPG, a remote attacker could possibly execute arbitrary code with the permissions of the user running GnuPG.
There is no known workaround at this time.
All GnuPG users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose "=app-crypt/gnupg-1.4*"
GnuPG may erroneously report a modified or unsigned message has a valid digital signature.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| app-crypt/gnupg | * | < 1.4.2.2 | >= 1.4.2.2 |
The GNU Privacy Guard, GnuPG, is a free replacement for the PGP suite of cryptographic software that may be used without restriction, as it does not rely on any patented algorithms. GnuPG can be used to digitally sign messages, a method of ensuring the authenticity of a message using public key cryptography.
OpenPGP is the standard that defines the format of digital signatures supported by GnuPG. OpenPGP signatures consist of multiple sections, in a strictly defined order. Tavis Ormandy of the Gentoo Linux Security Audit Team discovered that certain illegal signature formats could allow signed data to be modified without detection. GnuPG has previously attempted to be lenient when processing malformed or legacy signature formats, but this has now been found to be insecure.
A remote attacker may be able to construct or modify a digitally-signed message, potentially allowing them to bypass authentication systems, or impersonate another user.
There is no known workaround at this time.
All GnuPG users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=app-crypt/gnupg-1.4.2.2"
Applications relying on GnuPG to authenticate digital signatures may incorrectly believe a signature has been verified.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| app-crypt/gnupg | * | < 1.4.2.1 | >= 1.4.2.1 |
GnuPG (The GNU Privacy Guard) is a free replacement for PGP (Pretty Good Privacy). As GnuPG does not rely on any patented algorithms, it can be used without any restrictions. gpgv is the OpenPGP signature verification tool provided by the GnuPG system.
Tavis Ormandy of the Gentoo Linux Security Auditing Team discovered that automated systems relying on the return code of GnuPG or gpgv to authenticate digital signatures may be misled by malformed signatures. GnuPG documentation states that a return code of zero (0) indicates success, however gpg and gpgv may also return zero if no signature data was found in a detached signature file.
An attacker may be able to bypass authentication in automated systems relying on the return code of gpg or gpgv to authenticate digital signatures.
There is no known workaround at this time.
All GnuPG users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=app-crypt/gnupg-1.4.2.1"
Automated systems using GnuPG may leak plaintext portions of an encrypted message.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| app-crypt/gnupg | * | < 1.4.1 | >= 1.4.1 |
GnuPG is complete and free replacement for PGP, a tool for secure communication and data storage.
A flaw has been identified in an integrity checking mechanism of the OpenPGP protocol.
An automated system using GnuPG that allows an attacker to repeatedly discover the outcome of an integrity check (perhaps by observing the time required to return a response, or via overly verbose error messages) could theoretically reveal a small portion of plaintext.
There is no known workaround at this time.
All GnuPG users should upgrade to the latest version:
# emerge --sync # emerge --ask --oneshot --verbose ">=app-crypt/gnupg-1.4.1"
A bug in GnuPG allows ElGamal signing keys to be compromised, and a format string bug in the gpgkeys_hkp utility may allow arbitrary code execution.
| Package | Arch | Vulnerable | Unaffected |
|---|---|---|---|
| app-crypt/gnupg | * | <= 1.2.3-r4 | >= 1.2.3-r5 |
GnuPG is a popular open source signing and encryption tool.
Two flaws have been found in GnuPG 1.2.3.
First, ElGamal signing keys can be compromised. These keys are not commonly used, but this is "a significant security failure which can lead to a compromise of almost all ElGamal keys used for signing. Note that this is a real world vulnerability which will reveal your private key within a few seconds".
Second, there is a format string flaw in the 'gpgkeys_hkp' utility which "would allow a malicious keyserver in the worst case to execute an arbitrary code on the user's machine."
If you have used ElGamal keys for signing your private key can be compromised, and a malicious keyserver could remotely execute arbitrary code with the permissions of the user running gpgkeys_hkp.
There is no known workaround at this time.
All users who have created ElGamal signing keys should immediately revoke them. In addition, all Gentoo Linux machines with gnupg installed should be updated to use gnupg-1.2.3-r5 or higher:
# emerge sync # emerge -pv '>=app-crypt/gnupg-1.2.3-r5' # emerge '>=app-crypt/gnupg-1.2.3-r5' # emerge clean