First published: Fri Dec 22 2017(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
debian/enigmail | 2:2.2.4-0.2~deb10u1 2:2.1.3+ds1-4~deb10u2 2:2.2.4-0.3 | |
Enigmail | <1.9.9 | |
Debian | =8.0 | |
Debian | =9.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-17847 is considered a medium severity vulnerability due to the potential for signature spoofing.
To resolve CVE-2017-17847, it is recommended to upgrade Enigmail to version 1.9.9 or later.
CVE-2017-17847 is classified as a signature spoofing vulnerability.
Enigmail versions prior to 1.9.9 are affected by CVE-2017-17847.
Yes, CVE-2017-17847 affects Enigmail installations on Debian Linux versions 8.0 and 9.0.