First published: Fri Sep 20 2013(Updated: )
GnuPG 1.4.x, 2.0.x, and 2.1.x treats a key flags subpacket with all bits cleared (no usage permitted) as if it has all bits set (all usage permitted), which might allow remote attackers to bypass intended cryptographic protection mechanisms by leveraging the subkey.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Debian GnuPG | =1.4.0 | |
Debian GnuPG | =1.4.2 | |
Debian GnuPG | =1.4.3 | |
Debian GnuPG | =1.4.4 | |
Debian GnuPG | =1.4.5 | |
Debian GnuPG | =1.4.6 | |
Debian GnuPG | =1.4.8 | |
Debian GnuPG | =1.4.10 | |
Debian GnuPG | =1.4.11 | |
Debian GnuPG | =1.4.12 | |
Debian GnuPG | =1.4.13 | |
Debian GnuPG | =2.0 | |
Debian GnuPG | =2.0.1 | |
Debian GnuPG | =2.0.3 | |
Debian GnuPG | =2.0.4 | |
Debian GnuPG | =2.0.5 | |
Debian GnuPG | =2.0.6 | |
Debian GnuPG | =2.0.7 | |
Debian GnuPG | =2.0.8 | |
Debian GnuPG | =2.0.10 | |
Debian GnuPG | =2.0.11 | |
Debian GnuPG | =2.0.12 | |
Debian GnuPG | =2.0.13 | |
Debian GnuPG | =2.0.14 | |
Debian GnuPG | =2.0.15 | |
Debian GnuPG | =2.0.16 | |
Debian GnuPG | =2.0.17 | |
Debian GnuPG | =2.0.18 | |
Debian GnuPG | =2.0.19 | |
Debian GnuPG | =2.1.0-beta1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2013-4351 is classified as moderate, as it can potentially allow unauthorized use of cryptographic protections.
To fix CVE-2013-4351, update GnuPG to a version that addresses the issue, specifically version 1.4.14 or later for GnuPG 1.4.x and version 2.0.20 or later for GnuPG 2.0.x.
CVE-2013-4351 affects GnuPG versions 1.4.0 through 1.4.13 and 2.0.0 through 2.0.19.
Yes, CVE-2013-4351 can lead to data compromise by allowing attackers to misuse cryptographic keys.
Yes, CVE-2013-4351 specifically involves a vulnerability in how GnuPG handles key flags, impacting key management.