Bug 1193008 (CVE-2015-1606) - CVE-2015-1606 gnupg2: invalid memory read using a garbled keyring
Summary: CVE-2015-1606 gnupg2: invalid memory read using a garbled keyring
Alias: CVE-2015-1606
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On: 1193010 1193011
Blocks: 1193016
TreeView+ depends on / blocked
Reported: 2015-02-16 11:32 UTC by Vasyl Kaigorodov
Modified: 2021-02-17 05:38 UTC (History)
4 users (show)

Fixed In Version: GnuPG 2.1.2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-02-24 06:38:11 UTC

Attachments (Terms of Use)

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:

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


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.