CVE-2012-6085
published 2013-01-24CVE-2012-6085: The read_block function in g10/import.c in GnuPG 1.4.x before 1.4.13 and 2.0.x through 2.0.19, when importing a key, allows remote attackers to corrupt the…
PriorityP423medium5.8CVSS 2.0
AVNACMAuNCNIPAP
EPSS
2.91%
85.4th percentile
The read_block function in g10/import.c in GnuPG 1.4.x before 1.4.13 and 2.0.x through 2.0.19, when importing a key, allows remote attackers to corrupt the public keyring database or cause a denial of service (application crash) via a crafted length field of an OpenPGP packet.
Affected
28 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | gnupg2 | < gnupg2 2.0.19-2 (bookworm) | gnupg2 2.0.19-2 (bookworm) |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
| gnupg | gnupg | — | — |
CVSS provenance
nvdv2.05.8MEDIUMAV:N/AC:M/Au:N/C:N/I:P/A:P
osv5.8MEDIUM
vendor_debian5.8MEDIUM
vendor_redhat5.8MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
GnuPG vulnerability
vendor_ubuntu·2013-01-09
CVE-2012-6085 GnuPG vulnerability
Title: GnuPG vulnerability
Summary: GnuPG could be made to corrupt the keyring if it imported a specially
crafted key.
KB Sriram discovered that GnuPG incorrectly handled certain malformed keys.
If a user or automated system were tricked into importing a malformed key,
the GnuPG keyring could become corrupted.
Instructions: In general, a standard system update will make all the necessary changes.
Red Hat
GnuPG: read_block() corrupt key input validation
vendor_redhat·2012-12-29·CVSS 5.8
CVE-2012-6085 [MEDIUM] CWE-20 GnuPG: read_block() corrupt key input validation
GnuPG: read_block() corrupt key input validation
The read_block function in g10/import.c in GnuPG 1.4.x before 1.4.13 and 2.0.x through 2.0.19, when importing a key, allows remote attackers to corrupt the public keyring database or cause a denial of service (application crash) via a crafted length field of an OpenPGP packet.
Debian
CVE-2012-6085: gnupg2 - The read_block function in g10/import.c in GnuPG 1.4.x before 1.4.13 and 2.0.x t...
vendor_debian·2012·CVSS 5.8
CVE-2012-6085 [MEDIUM] CVE-2012-6085: gnupg2 - The read_block function in g10/import.c in GnuPG 1.4.x before 1.4.13 and 2.0.x t...
The read_block function in g10/import.c in GnuPG 1.4.x before 1.4.13 and 2.0.x through 2.0.19, when importing a key, allows remote attackers to corrupt the public keyring database or cause a denial of service (application crash) via a crafted length field of an OpenPGP packet.
Scope: local
bookworm: resolved (fixed in 2.0.19-2)
bullseye: resolved (fixed in 2.0.19-2)
forky: resolved (fixed in 2.0.19-2)
sid: resolved (fixed in 2.0.19-2)
trixie: resolved (fixed in 2.0.19-2)
GHSA
GHSA-5m4p-hwr3-qvm6: The read_block function in g10/import
ghsa_unreviewed·2022-05-17
CVE-2012-6085 [MEDIUM] CWE-20 GHSA-5m4p-hwr3-qvm6: The read_block function in g10/import
The read_block function in g10/import.c in GnuPG 1.4.x before 1.4.13 and 2.0.x through 2.0.19, when importing a key, allows remote attackers to corrupt the public keyring database or cause a denial of service (application crash) via a crafted length field of an OpenPGP packet.
OSV
CVE-2012-6085: The read_block function in g10/import
osv·2013-01-24·CVSS 5.8
CVE-2012-6085 [MEDIUM] CVE-2012-6085: The read_block function in g10/import
The read_block function in g10/import.c in GnuPG 1.4.x before 1.4.13 and 2.0.x through 2.0.19, when importing a key, allows remote attackers to corrupt the public keyring database or cause a denial of service (application crash) via a crafted length field of an OpenPGP packet.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2012-6085 GnuPG: read_block() corrupt key input validation [fedora-all]
bugzilla·2013-10-08·CVSS 5.8
CVE-2012-6085 [MEDIUM] CVE-2012-6085 GnuPG: read_block() corrupt key input validation [fedora-all]
CVE-2012-6085 GnuPG: read_block() corrupt key input validation [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When creating a Bodhi update request, please use the bodhi submission link
noted in the next comment(s). This will include the bug IDs of this
tracking bug as well as the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
Bodhi notes field when available.
Please note: this issue affec
Bugzilla
CVE-2012-6085 CVE-2013-4402 gnupg2: various flaws [fedora-all]
bugzilla·2013-10-07·CVSS 5.8
CVE-2012-6085 [MEDIUM] CVE-2012-6085 CVE-2013-4402 gnupg2: various flaws [fedora-all]
CVE-2012-6085 CVE-2013-4402 gnupg2: various flaws [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When creating a Bodhi update request, please use the bodhi submission link
noted in the next comment(s). This will include the bug IDs of this
tracking bug as well as the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
Bodhi notes field when available.
Please note: this issue affects multiple s
Bugzilla
CVE-2012-6085 GnuPG: read_block() corrupt key input validation [epel-5]
bugzilla·2013-01-16·CVSS 5.8
CVE-2012-6085 [MEDIUM] CVE-2012-6085 GnuPG: read_block() corrupt key input validation [epel-5]
CVE-2012-6085 GnuPG: read_block() corrupt key input validation [epel-5]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora EPEL.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When creating a Bodhi update request, please use the bodhi submission link
noted in the next comment(s). This will include the bug IDs of this
tracking bug as well as the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
Bodhi notes field when available.
epel-5 tracking bug for gnup
Bugzilla
CVE-2012-6085 GnuPG: read_block() corrupt key input validation
bugzilla·2013-01-02·CVSS 5.8
CVE-2012-6085 [MEDIUM] CVE-2012-6085 GnuPG: read_block() corrupt key input validation
CVE-2012-6085 GnuPG: read_block() corrupt key input validation
KB Sriram ([email protected]) reports:
Versions of GnuPG <= 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:
https://bugs.g10code.com/gnupg/issue1455
The subsequent memory access violation was discovered and reported in
a private em
http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git%3Ba=commitdiff%3Bh=f0b33b6fb8e0586e9584a7a409dcc31263776a67http://lists.fedoraproject.org/pipermail/package-announce/2013-January/095513.htmlhttp://lists.fedoraproject.org/pipermail/package-announce/2013-January/095516.htmlhttp://rhn.redhat.com/errata/RHSA-2013-1459.htmlhttp://www.mandriva.com/security/advisories?name=MDVSA-2013:001http://www.openwall.com/lists/oss-security/2013/01/01/6http://www.securityfocus.com/bid/57102http://www.ubuntu.com/usn/USN-1682-1https://bugs.g10code.com/gnupg/issue1455https://bugzilla.redhat.com/show_bug.cgi?id=891142https://exchange.xforce.ibmcloud.com/vulnerabilities/80990http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git%3Ba=commitdiff%3Bh=f0b33b6fb8e0586e9584a7a409dcc31263776a67http://lists.fedoraproject.org/pipermail/package-announce/2013-January/095513.htmlhttp://lists.fedoraproject.org/pipermail/package-announce/2013-January/095516.htmlhttp://rhn.redhat.com/errata/RHSA-2013-1459.htmlhttp://www.mandriva.com/security/advisories?name=MDVSA-2013:001http://www.openwall.com/lists/oss-security/2013/01/01/6http://www.securityfocus.com/bid/57102http://www.ubuntu.com/usn/USN-1682-1https://bugs.g10code.com/gnupg/issue1455https://bugzilla.redhat.com/show_bug.cgi?id=891142https://exchange.xforce.ibmcloud.com/vulnerabilities/80990
2013-01-24
Published