Bug 510503 - gpg invalid packet error decrypting certain files
Summary: gpg invalid packet error decrypting certain files
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: gnupg
Version: 5.3
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Tomas Mraz
QA Contact: Ondrej Moriš
URL: https://bugs.g10code.com/gnupg/issue537
Depends On:
Blocks: 510500 602669
TreeView+ depends on / blocked
Reported: 2009-07-09 14:31 UTC by Casey Dahlin
Modified: 2018-11-14 19:55 UTC (History)
4 users (show)

Fixed In Version: gnupg-1.4.5-15
Doc Type: Bug Fix
Doc Text:
Clone Of: 510500
Last Closed: 2013-09-23 11:03:35 UTC

Attachments (Terms of Use)
Reproducer (Top level of tar is NOT A DIRECTORY. Unpack carefully) (12.04 KB, application/x-gzip)
2009-07-09 14:31 UTC, Casey Dahlin
no flags Details

Description Casey Dahlin 2009-07-09 14:31:54 UTC
Created attachment 351079 [details]
Reproducer (Top level of tar is NOT A DIRECTORY. Unpack carefully)

Confirmed for RHEL 5 as well.

+++ This bug was initially created as a clone of Bug #510500 +++

Created an attachment (id=351077)
Reproducer (Top level of tar is NOT A DIRECTORY. Unpack carefully)

Description of problem:
Decrypting certain data (length of message seems to be the determining factor) causes this error message:

gpg: [don't know]: invalid packet (ctb=14)

This patch seems to fix it for the customer:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Unpack the attached tar in a new folder
2. Run:
echo foobar | gpg -d --passphrase-fd 0 --homedir dot.gnupg --yes -o 2019.dat 2019.dat.gpg
Actual results:
Error message

Expected results:
The file is decrypted

Additional info:
Customer claims this also reproduces on RHEL 3 and 5. In the case of RHEL 5, I will clone the bug if I can reproduce it myself.

Comment 1 Nalin Dahyabhai 2009-07-13 18:29:55 UTC
The patch used in 1.4.6 ended up being a bit different; we should use that one instead.  Has a bit of overlap with changes to fix CVE-2006-6235, so needs a bit of adjusting.

Comment 7 Tomas Mraz 2010-05-05 18:29:28 UTC
Patch is here:

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