CVE-2012-6085: Input Validation

First published: Wed Jan 02 2013(Updated: )

KB Sriram (kbsriram) reports: Versions of GnuPG &lt;= 1.4.12 are vulnerable to memory access violations and public keyring database corruption when importing public keys that have been manipulated. An OpenPGP key can be fuzzed in such a way that gpg segfaults (or has other memory access violations) when importing the key. The key may also be fuzzed such that gpg reports no errors when examining the key (eg: "gpg the_bad_key.pkr") but importing it causes gpg to corrupt its public keyring database. The database corruption issue was first reported on Dec 6th, through the gpg bug tracking system: <a href="https://bugs.g10code.com/gnupg/issue1455">https://bugs.g10code.com/gnupg/issue1455</a> The subsequent memory access violation was discovered and reported in a private email with the maintainer on Dec 20th. A zip file with keys that causes segfaults and other errors is available at <a href="http://dl.dropbox.com/u/18852638/gnupg-issues/1455.zip">http://dl.dropbox.com/u/18852638/gnupg-issues/1455.zip</a> and includes a log file that demonstrates the issues [on MacOS X and gpg 1.4.11] A new version of gpg -- 1.4.13 -- that addressed both these issues, was independently released by the maintainer on Dec 20th. The simplest solution is to upgrade all gpg installs to 1.4.13. [Workarounds: A corrupted database may be recovered by manually copying back the pubring.gpg~ backup file. Certain errors may also be prevented by never directly importing a key, but first just "looking" at the key (eg: "gpg bad_key.pkr"). However, this is not guaranteed to work in all cases; though upgrading to 1.4.13 does work for the issues reported.] Discovery: The problem was discovered during a byte-fuzzing test of OpenPGP certificates for an unrelated application. Each byte in turn was replaced by a random byte, and the modified certificate fed to the application to check that it handled errors correctly. Gpg was used as a control, but it itself turned out to have errors related to packet parsing. The errors are generally triggered when fuzzing the length field of OpenPGP packets, which cascades into subsequent errors in certain situations. External references: <a href="https://bugs.g10code.com/gnupg/issue1455">https://bugs.g10code.com/gnupg/issue1455</a> <a href="http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commitdiff;h=f0b33b6fb8e0586e9584a7a409dcc31263776a67">http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commitdiff;h=f0b33b6fb8e0586e9584a7a409dcc31263776a67</a>

Credit: secalert@redhat.com

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

• collector/nvd-index
• agent/type
• agent/first-publish-date
• agent/softwarecombine
• collector/mitre-cve
• source/MITRE
• collector/redhat-bugzilla
• source/Red Hat
• alias/CVE-2012-6085
• agent/last-modified-date
• agent/author
• agent/severity
• agent/references
• agent/weakness
• agent/tags
• agent/event
• agent/description
• agent/trending
• vendor/gnupg
• canonical/gnupg gnupg
• version/gnupg gnupg/1.4.0
• version/gnupg gnupg/1.4.2
• version/gnupg gnupg/1.4.3
• version/gnupg gnupg/1.4.4
• version/gnupg gnupg/1.4.5
• version/gnupg gnupg/1.4.8
• version/gnupg gnupg/1.4.10
• version/gnupg gnupg/1.4.11
• version/gnupg gnupg/1.4.12
• version/gnupg gnupg/2.0
• version/gnupg gnupg/2.0.1
• version/gnupg gnupg/2.0.3
• version/gnupg gnupg/2.0.4
• version/gnupg gnupg/2.0.5
• version/gnupg gnupg/2.0.6
• version/gnupg gnupg/2.0.7
• version/gnupg gnupg/2.0.8
• version/gnupg gnupg/2.0.10
• version/gnupg gnupg/2.0.11
• version/gnupg gnupg/2.0.12
• version/gnupg gnupg/2.0.13
• version/gnupg gnupg/2.0.14
• version/gnupg gnupg/2.0.15
• version/gnupg gnupg/2.0.16
• version/gnupg gnupg/2.0.17
• version/gnupg gnupg/2.0.18
• version/gnupg gnupg/2.0.19