GnuPG patches a critical GPGME flaw that could allow code execution
The GnuPG project released GPGME 2.3.1 on Nov. 19, fixing a critical flaw in all earlier versions that could let an attacker run code on a machine that handles a crafted key.
A key carrying a very long user ID triggers a double free in the library's status-line reader, Werner Koch wrote in the release announcement. The freed memory can be used to exfiltrate data from applications — by sending them signed data, for instance — and Koch said remote code execution cannot be ruled out.
Everything linking GPGME is affected, whether as a shared library, a DLL, or statically linked: most mail clients, many XMPP clients, Samba, Flatpak, Gpg4win, and GnuPG Desktop. Statically linked binaries must be rebuilt against 2.3.1, and the project published a patch for older versions. GPGMPP and GPGMEQT need no update.
Johan Carlsson found the bug; GitLab told GnuPG on Nov. 12. Disclosure was set for Nov. 25 but moved to Nov. 20 because of the new Ruby2Shell bug.