Improper Verification of Cryptographic Signature Affecting enigmail package, versions <2:1.9.9-1~deb8u1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIAN8-ENIGMAIL-324093
- published27 Dec 2017
- disclosed27 Dec 2017
Introduced: 27 Dec 2017
CVE-2017-17847 (opens in a new tab)How to fix?
Upgrade Debian:8 enigmail to version 2:1.9.9-1~deb8u1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream enigmail package and not the enigmail package as distributed by Debian.
See How to fix? for Debian:8 relevant fixed versions and status.
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.
References
- https://security-tracker.debian.org/tracker/CVE-2017-17847
- https://www.debian.org/security/2017/dsa-4070
- https://lists.debian.org/debian-lts-announce/2017/12/msg00021.html
- https://enigmail.net/download/other/Enigmail%20Pentest%20Report%20by%20Cure53%20-%20Excerpt.pdf
- https://lists.debian.org/debian-security-announce/2017/msg00333.html
- https://sourceforge.net/p/enigmail/bugs/709/
- https://www.mail-archive.com/enigmail-users@enigmail.net/msg04280.html
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2017-17847
- https://www.mail-archive.com/enigmail-users%40enigmail.net/msg04280.html