First published: Wed Feb 15 2006(Updated: )
gpgv in GnuPG before 1.4.2.1, when using unattended signature verification, returns a 0 exit code in certain cases even when the detached signature file does not carry a signature, which could cause programs that use gpgv to assume that the signature verification has succeeded. Note: this also occurs when running the equivalent command "gpg --verify".
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.0 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.0.1 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.0.2 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.0.3 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.0.3b | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.0.4 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.0.5 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.0.6 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.0.7 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.2 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.2.1 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.2.2 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.2.2-rc1 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.2.3 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.2.4 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.2.5 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.2.6 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.2.7 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.3.3 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.3.4 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.4 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.4.1 | |
GnuPGME (Gnu Privacy Guard Message Envelopes) | =1.4.2 |
http://www.slackware.com/security/viewer.php?l=slackware-security&y=2006&m=slackware-security.476477
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2006-0455 is considered a medium severity vulnerability due to its potential to mislead programs into assuming a successful signature verification.
To fix CVE-2006-0455, upgrade to GnuPG version 1.4.2.1 or later, where this issue has been resolved.
CVE-2006-0455 affects GnuPG versions prior to 1.4.2.1, specifically versions 1.0 to 1.4.1.
CVE-2006-0455 can cause gpgv to return a success exit code even when a detached signature file lacks a valid signature, leading to false confidence in security.
While upgrading GnuPG is the best solution for CVE-2006-0455, using additional verification processes outside of gpgv could serve as a temporary workaround.