Bug 1193008 (CVE-2015-1606)

Summary:	CVE-2015-1606 gnupg2: invalid memory read using a garbled keyring
Product:	[Other] Security Response	Reporter:	Vasyl Kaigorodov <vkaigoro>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	bcl, carnil, rdieter, tmraz
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	GnuPG 2.1.2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-24 06:38:11 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1193010, 1193011
Bug Blocks:	1193016

Description Vasyl Kaigorodov 2015-02-16 11:32:05 UTC

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 11:39:38 UTC

Created gnupg2 tracking bugs for this issue:

Affects: fedora-all [bug 1193011]

Comment 2 Vasyl Kaigorodov 2015-02-16 11:39:41 UTC

Created gnupg tracking bugs for this issue:

Affects: fedora-all [bug 1193010]

Comment 3 Huzaifa S. Sidhpurwala 2015-02-24 06:29:21 UTC

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