GLSA 200602-10: GnuPG: Incorrect signature verification

Title:GnuPG: Incorrect signature verification
Bugs: #122721


Applications relying on GnuPG to authenticate digital signatures may incorrectly believe a signature has been verified.


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.

Affected packages

Package Vulnerable Unaffected Architecture(s)
app-crypt/gnupg < >= All supported architectures


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-"



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


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 or alternatively, you may file a bug at


Copyright 2010 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.

Thank you!