GnuPG duplicate keys code execution
| gnupg-keys-code-execution (41547) |  High Risk |
Description:
GnuPG could allow a remote attacker to execute arbitrary code on the system, caused by a memory corruption error while duplicating user IDs. By importing OpenPGP keys from key servers using specially-crafted duplicate keys, a remote attacker could exploit this vulnerability to corrupt memory and execute arbitrary code or cause a denial of service.
Platforms Affected:
- GNU, Privacy Guard 1.4.8
- GNU, Privacy Guard 2.0.8
Remedy:
Upgrade to the latest version of GnuPG (1.4.9 or 2.0.9 or later), available from the GNU Web site. See References.
Consequences:
Gain Access
References:
- Gentoo Bugzilla Bug 214990, app-crypt/gnupg =1.4.8, =2.0.8 Memory corruption when importing keys (CVE-2008-1530) at https://bugs.gentoo.org/show_bug.cgi?id=214990.
- GNU Web site, The GNU Privacy Guard at http://www.gnupg.org/.
- gnupg Security Fix, Issue 894, segv when importing keys with duplicated ids at https://bugs.g10code.com/gnupg/issue894.
- oCERT Advisories #2008-01, GnuPG memory corruption at http://www.ocert.org/advisories/ocert-2008-1.html.
- BID-28487: GnuPG Duplicated Key Import Memory Corruption Vulnerability
- CVE-2008-1530: GnuPG (gpg) 1.4.8 and 2.0.8 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via crafted duplicate keys that are imported from key servers, which triggers memory corruption around deduplication of user IDs.
- SA29568: GnuPG Duplicated IDs Memory Corruption
- VUPEN/ADV-2008-1056: GnuPG Duplicated User IDs Remote Memory Corruption Vulnerability
Reported:
Mar 27, 2008
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net