Bug 1193009 (CVE-2015-1607)

Summary:	CVE-2015-1607 gnupg2: memcpy with overlapping ranges (keybox_search.c)
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, sonu.khan, 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:26 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:39:08 UTC

Information leak was reported [1] in GnuPG 2.
This issue was fixed by the below upstream commit:
http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=2183683bd633818dd031b090b5530951de76f392

[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:40:05 UTC

Created gnupg2 tracking bugs for this issue:

Affects: fedora-all [bug 1193011]

Comment 2 Vasyl Kaigorodov 2015-02-16 11:40:07 UTC

Created gnupg tracking bugs for this issue:

Affects: fedora-all [bug 1193010]

Comment 3 Huzaifa S. Sidhpurwala 2015-02-24 06:32:31 UTC

This issue is similar to CVE-2015-1606, in which a specially-crafted keyring would be required to actually cause a 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/.

Comment 4 Sonu Khan 2020-01-28 13:28:55 UTC

Is there any steps for mitigation?
Also how to reproduce this case in our local system.