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
Link | Resource |
---|---|
https://enigmail.net/download/other/Enigmail%20Pentest%20Report%20by%20Cure53%20-%20Excerpt.pdf | Vendor Advisory |
https://lists.debian.org/debian-lts-announce/2017/12/msg00021.html | |
https://lists.debian.org/debian-security-announce/2017/msg00333.html | Third Party Advisory |
https://sourceforge.net/p/enigmail/bugs/709/ | Third Party Advisory |
https://www.debian.org/security/2017/dsa-4070 | Third Party Advisory |
https://www.mail-archive.com/enigmail-users%40enigmail.net/msg04280.html |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2017-12-22T23:00:00
Updated: 2018-02-02T10:57:01
Reserved: 2017-12-22T00:00:00
Link: CVE-2017-17847
JSON object: View
NVD Information
Status : Modified
Published: 2017-12-27T17:08:19.873
Modified: 2023-11-07T02:41:47.640
Link: CVE-2017-17847
JSON object: View
Redhat Information
No data.
CWE