Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1193008 - (CVE-2015-1606) CVE-2015-1606 gnupg2: invalid memory read using a garbled keyring
CVE-2015-1606 gnupg2: invalid memory read using a garbled keyring
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20150213,reported=2...
: Security
Depends On: 1193010 1193011
Blocks: 1193016
  Show dependency treegraph
 
Reported: 2015-02-16 06:32 EST by Vasyl Kaigorodov
Modified: 2015-02-24 01:38 EST (History)
5 users (show)

See Also:
Fixed In Version: GnuPG 2.1.2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-02-24 01:38:11 EST
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 Vasyl Kaigorodov 2015-02-16 06:32:05 EST
It was reported [1] that GnuPG2 keyring DB code did not reject packets which don't belong into a keyring, which may lead to invalid read of sizeof (int).
It was fixed by the below upstream commit:
http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=f0f71a721ccd7ab9e40b8b6b028b59632c0cc648

[1]: https://blog.fuzzing-project.org/5-Multiple-issues-in-GnuPG-found-through-keyring-fuzzing-TFPA-0012015.html
Comment 1 Vasyl Kaigorodov 2015-02-16 06:39:38 EST
Created gnupg2 tracking bugs for this issue:

Affects: fedora-all [bug 1193011]
Comment 2 Vasyl Kaigorodov 2015-02-16 06:39:41 EST
Created gnupg tracking bugs for this issue:

Affects: fedora-all [bug 1193010]
Comment 3 Huzaifa S. Sidhpurwala 2015-02-24 01:29:21 EST
In order to exploit this flaw, one would need specially-crafted gpg keyring files. This would result in a OOB read condition and gpg2 binary would crash.


Statement:

Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

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