The keyring DB in GnuPG before 2.1.2 does not properly handle invalid packets, which allows remote attackers to cause a denial of service (invalid read and use-after-free) via a crafted keyring file.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
| Link | Tags |
|---|---|
| https://blog.fuzzing-project.org/5-Multiple-issues-in-GnuPG-found-through-keyring-fuzzing-TFPA-0012015.html | third party advisory |
| http://www.debian.org/security/2015/dsa-3184 | third party advisory |
| http://www.openwall.com/lists/oss-security/2015/02/13/14 | third party advisory mailing list |
| http://www.openwall.com/lists/oss-security/2015/02/14/6 | third party advisory mailing list |
| http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git%3Ba=commit%3Bh=f0f71a721ccd7ab9e40b8b6b028b59632c0cc648 | |
| http://www.securitytracker.com/id/1031876 | vdb entry third party advisory |