First published: Mon Jun 11 2018(Updated: )
Marcus Brinkmann discovered that during decryption or verification, GnuPG did not properly filter out terminal sequences when reporting the original filename. An attacker could use this to specially craft a file that would cause an application parsing GnuPG output to incorrectly interpret the status of the cryptographic operation reported by GnuPG. (CVE-2018-12020) Lance Vick discovered that GnuPG did not enforce configurations where key certification required an offline primary Certify key. An attacker with access to a signing subkey could generate certifications that appeared to be valid. This issue only affected Ubuntu 18.04 LTS. (CVE-2018-9234)
Affected Software | Affected Version | How to fix |
---|---|---|
All of | ||
ubuntu/gnupg | <2.2.4-1ubuntu1.1 | 2.2.4-1ubuntu1.1 |
=18.04 | ||
All of | ||
ubuntu/gpg | <2.2.4-1ubuntu1.1 | 2.2.4-1ubuntu1.1 |
=18.04 | ||
All of | ||
ubuntu/gnupg | <2.1.15-1ubuntu8.1 | 2.1.15-1ubuntu8.1 |
=17.10 | ||
All of | ||
ubuntu/gnupg | <1.4.20-1ubuntu3.2 | 1.4.20-1ubuntu3.2 |
=16.04 | ||
All of | ||
ubuntu/gnupg | <1.4.16-1ubuntu2.5 | 1.4.16-1ubuntu2.5 |
=14.04 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of USN-3675-1 is high.
The affected software for USN-3675-1 is GnuPG.
An attacker can exploit USN-3675-1 by crafting a file that causes a application parsing GnuPG output to incorrectly interpret the status.
To fix USN-3675-1, update GnuPG to version 2.2.4-1ubuntu1.1 or later.
You can find more information about USN-3675-1 at the following references: - [CVE-2018-12020](https://ubuntu.com/security/CVE-2018-12020) - [CVE-2018-9234](https://ubuntu.com/security/CVE-2018-9234) - [USN-3675-3](https://ubuntu.com/security/notices/USN-3675-3)