GnuPG: Incorrect signature verification — GLSA 200602-10

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

Affected Packages

app-crypt/gnupg on all architectures
Affected versions < 1.4.2.1
Unaffected versions >= 1.4.2.1

Background

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.

Description

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.

Impact

An attacker may be able to bypass authentication in automated systems relying on the return code of gpg or gpgv to authenticate digital signatures.

Workaround

There is no known workaround at this time.

Resolution

All GnuPG users should upgrade to the latest version:

 # emerge --sync
 # emerge --ask --oneshot --verbose ">=app-crypt/gnupg-1.4.2.1"

References

Release Date
February 18, 2006

Latest Revision
February 18, 2006: 01

Severity
normal

Exploitable
remote

Bugzilla entries