Bug 1010137 (CVE-2013-4351) - CVE-2013-4351 gnupg: treats no-usage-permitted keys as all-usages-permitted
Summary: CVE-2013-4351 gnupg: treats no-usage-permitted keys as all-usages-permitted
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2013-4351
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard: impact=low,public=20130312,reported=2...
Depends On: 1010140 1010141 1010142 1015736 1015737 1015738 1015739 1015740 1015741 1015743 1018109 1018110
Blocks: 1010144 1015687
TreeView+ depends on / blocked
 
Reported: 2013-09-20 05:20 UTC by Ratul Gupta
Modified: 2019-06-08 19:43 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-22 06:26:37 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:1458 normal SHIPPED_LIVE Moderate: gnupg security update 2013-10-24 19:22:57 UTC
Red Hat Product Errata RHSA-2013:1459 normal SHIPPED_LIVE Moderate: gnupg2 security update 2013-10-24 19:22:46 UTC

Description Ratul Gupta 2013-09-20 05:20:21 UTC
GnuPG and GnuPG2 are found to have a flaw, where the key flags are misinterpreted, which could possibly lead to a breach of confidentiality or a mistaken identity verification. Key flags are the packets, that indicated the capabilities of the key, represented as binary flags. The issue is that if a key or subkey has this "key flags" subpacket attached with all bits cleared (off), GnuPG currently treats the key as having all bits set (on), though the thing to note is that the keys with this sort of marker are very rare in the wild.
The risks are unlikely today, and they are not particularly dangerous, but the keyholder's stated intent of separating out keys by context of use is being ignored, so there is a window of vulnerability that should not be open.

References:
http://seclists.org/oss-sec/2013/q3/599
https://bugs.gentoo.org/show_bug.cgi?id=484836
https://bugzilla.novell.com/show_bug.cgi?id=840510

Comment 1 Ratul Gupta 2013-09-20 05:28:41 UTC
Patches are available, but appear to only be applied on the development
branch (2.1.x).  So stable branches 1.4.x and 2.0.x remain vulnerable at
the moment.

Comment 2 Ratul Gupta 2013-09-20 05:31:39 UTC
Created gnupg2 tracking bugs for this issue:

Affects: fedora-all [bug 1010141]
Affects: epel-5 [bug 1010142]

Comment 3 Ratul Gupta 2013-09-20 05:31:57 UTC
Created gnupg tracking bugs for this issue:

Affects: fedora-all [bug 1010140]

Comment 4 Fedora Update System 2013-10-10 14:47:56 UTC
gnupg-1.4.15-1.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2013-10-12 00:02:46 UTC
gnupg-1.4.15-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 13 errata-xmlrpc 2013-10-24 15:25:02 UTC
This issue has been addressed in following products:

  Red Hat Enterprise Linux 5
  Red Hat Enterprise Linux 6

Via RHSA-2013:1459 https://rhn.redhat.com/errata/RHSA-2013-1459.html

Comment 14 errata-xmlrpc 2013-10-24 15:27:08 UTC
This issue has been addressed in following products:

  Red Hat Enterprise Linux 5

Via RHSA-2013:1458 https://rhn.redhat.com/errata/RHSA-2013-1458.html

Comment 15 Fedora Update System 2013-11-13 02:26:12 UTC
gnupg-1.4.15-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


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