Vulnerabilities · 2017 · Enigmail
CVE-2017-17847
Enigmail vulnerability
An issue was discovered in Enigmail before 1.9.9. Signature spoofing is possible because the UI does not properly distinguish between an attachment signature, and a signature that applies to the entire containing message, aka TBE-01-021. This is demonstrated by an e-mail message with an attachment that is a signed e-mail message in message/rfc822 format.
Affected products
Enigmail, Debian Linux. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Enigmail runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- enigmail.net/download/other/Enigmail%20Pentest%20Report%20by%20Cure53%20-%20Excerpt.pdf · Vendor Advisory
- lists.debian.org/debian-security-announce/2017/msg00333.html · Third Party Advisory
- sourceforge.net/p/enigmail/bugs/709/ · Third Party Advisory
- www.debian.org/security/2017/dsa-4070 · Third Party Advisory
- lists.debian.org/debian-lts-announce/2017/12/msg00021.html
- www.mail-archive.com/enigmail-users%40enigmail.net/msg04280.html
- nvd.nist.gov/vuln/detail/CVE-2017-17847
- cve.org/CVERecord?id=CVE-2017-17847
More vulnerabilities in Enigmail products
CVE-2019-14664CVE-2019-12269CVE-2018-15586CVE-2018-12019CVE-2017-17848CVE-2017-17846CVE-2017-17845CVE-2017-17844All 14
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.