CVE-2017-17844 json
An issue was discovered in Enigmail before 1.9.9.
published 2017-12-22 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-8991
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
An issue was discovered in Enigmail before 1.9.9. A remote attacker can obtain cleartext content by sending an encrypted data block (that the attacker cannot directly decrypt) to a victim, and relying on the victim to automatically decrypt that block and then send it back to the attacker as quoted text, aka the TBE-01-005 "replay" issue.
Patch / fix
- enigmail enigmail 1.9.9
- enigmail Debian 11 2:1.9.9-1
debian advisories DEBIAN-CVE-2017-17844
- enigmail Ubuntu 14.04 LTS 2:1.9.9-0ubuntu0.14.04.1
- enigmail Ubuntu 16.04 LTS 2:1.9.9-0ubuntu0.16.04.1
ubuntu advisories UBUNTU-CVE-2017-17844
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Exploit prediction
1.35% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-319 Cleartext Transmission of Sensitive Information
References
-
debian.org
/security/2017/dsa-4070
vendor-advisory, third-party-advisory
-
enigmail.net
/download/other/Enigmail%20Pentest%20Report%20by%20Cure53%20-%20Excerpt.pdf
third-party-advisory, vendor-advisory
-
lists.debian.org
/debian-security-announce/2017/msg00333.html
third-party-advisory
- mail-archive.com /enigmail-users%40enigmail.net/msg04280.html
-
lists.debian.org
/debian-lts-announce/2017/12/msg00021.html
mailing-list
Sources
- CVE List CVE-2017-17844
- NVD CVE-2017-17844
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.