Bug 183484 - CVE-2006-0455 gpg will quietly exit when attempting to verify a malformed message
CVE-2006-0455 gpg will quietly exit when attempting to verify a malformed mes...
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: gnupg (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Mike McLean
: Security
Depends On:
Blocks: 183726 183727
  Show dependency treegraph
Reported: 2006-03-01 08:56 EST by Josh Bressers
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version: RHSA-2006-0266
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-15 11:31:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2006:0266 normal SHIPPED_LIVE Important: gnupg security update 2006-03-15 00:00:00 EST

  None (edit)
Description Josh Bressers 2006-03-01 08:56:21 EST
+++ This bug was initially created as a clone of Bug #181822 +++

The Gentoo project identified a security related bug in GnuPG.  When
using any current version of GnuPG for unattended signature
verification (e.g. by scripts and mail programs), false positive
signature verification of detached signatures may occur.

This is primarily an issue since gpg return 0 on what should be a failure.  This
will break automated scripts.


A reproducer for RHEL can be found here:
(The Background section near the bottom)

This issue also affects RHEL2.1 and RHEL3
Comment 4 Red Hat Bugzilla 2006-03-15 11:31:48 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.