Bug 183726 - 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...
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: gnupg (Show other bugs)
2.1
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tomas Mraz
source=vendorsec,reported=20060213,pu...
: Security
Depends On: 183484
Blocks:
  Show dependency treegraph
 
Reported: 2006-03-02 23:27 EST by Nalin Dahyabhai
Modified: 2012-06-20 12:03 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 12:03:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Nalin Dahyabhai 2006-03-02 23:27:17 EST
+++ This bug was initially created as a clone of Bug #183484 +++

+++ 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.

http://marc.theaimsgroup.com/?l=gnupg-devel&m=113999098729114&w=2


A reproducer for RHEL can be found here:
http://lists.gnupg.org/pipermail/gnupg-announce/2006q1/000211.html
(The Background section near the bottom)

This issue also affects RHEL2.1 and RHEL3
Comment 1 Jiri Pallich 2012-06-20 12:03:41 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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