Enigmail
14 vulnerabilities.
All published vulnerabilities with a CVE number in Enigmail products, newest first, with severity and references.
| CVE | Summary | Published | CVSS |
|---|---|---|---|
| CVE-2019-14664 | Enigmail: In Enigmail below 2.1, an attacker in possession of PGP encrypted emails can wrap them as sub-parts within a crafted multipart email. The encrypted … | 2019-08-05 | 6.5 |
| CVE-2019-12269 | Enigmail: Enigmail before 2.0.11 allows PGP signature spoofing: for an inline PGP message, an attacker can cause the product to display a "correctly signed" … | 2019-05-21 | 7.5 |
| CVE-2018-15586 | Enigmail: Enigmail before 2.0.6 is prone to to OpenPGP signatures being spoofed for arbitrary messages using a PGP/INLINE signature wrapped within a … | 2019-02-11 | 6.5 |
| CVE-2018-12019 | Enigmail: The signature verification routine in Enigmail before 2.0.7 interprets user ids as status/control messages and does not correctly keep track of the … | 2018-06-13 | 7.5 |
| CVE-2017-17848 | Enigmail: An issue was discovered in Enigmail before 1.9.9. In a variant of CVE-2017-17847, signature spoofing is possible for multipart/related messages … | 2017-12-27 | 7.5 |
| CVE-2017-17847 | Enigmail: An issue was discovered in Enigmail before 1.9.9. Signature spoofing is possible because the UI does not properly distinguish between an attachment … | 2017-12-27 | 7.5 |
| CVE-2017-17846 | Enigmail: An issue was discovered in Enigmail before 1.9.9. Regular expressions are exploitable for Denial of Service, because of attempts to match … | 2017-12-27 | 7.5 |
| CVE-2017-17845 | Enigmail: An issue was discovered in Enigmail before 1.9.9. Improper Random Secret Generation occurs because Math.Random() is used by pretty Easy privacy … | 2017-12-27 | 7.3 |
| CVE-2017-17844 | Enigmail: An issue was discovered in Enigmail before 1.9.9. A remote attacker can obtain cleartext content by sending an encrypted data block (that the … | 2017-12-27 | 6.5 |
| CVE-2017-17843 | Enigmail: An issue was discovered in Enigmail before 1.9.9 that allows remote attackers to trigger use of an intended public key for encryption, because … | 2017-12-27 | 5.9 |
| CVE-2014-5369 | Enigmail: Enigmail 1.7.x before 1.7.2 sends emails in plaintext when encryption is enabled and only BCC recipients are specified, which allows remote … | 2014-09-08 | 4.3 |
| CVE-2007-1264 | Enigmail: Enigmail 0.94.2 and earlier does not properly use the --status-fd argument when invoking GnuPG, which prevents Enigmail from visually … | 2007-03-06 | 5.0 |
| CVE-2006-5877 | Enigmail: The enigmail extension before 0.94.2 does not properly handle large, encrypted file e-mail attachments, which allows remote attackers to cause a … | 2007-02-23 | 7.8 |
| CVE-2005-3256 | Enigmail: The key selection dialogue in Enigmail before 0.92.1 can incorrectly select a key with a user ID that does not have additional information, which … | 2005-10-18 | 5.0 |
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Too many to
patch at once?
Providers for vulnerability management find the affected systems in your environment, set the order and keep the patching going.