Skip to content
Fencer Intel
high 7.5

CVE-2018-12019 json

The signature verification routine in Enigmail before 2.0.7 interprets user ids as status/control messages and does not correctly keep trac…

published 8y ago modified 4mo ago also EUVD-2018-4010

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 81%
public exploits
0
none known

Summary

The signature verification routine in Enigmail before 2.0.7 interprets user ids as status/control messages and does not correctly keep track of the status of multiple signatures, which allows remote attackers to spoof arbitrary email signatures via public keys containing crafted primary user ids.

Patch / fix

  • enigmail enigmail 2.0.7
  • enigmail Debian 11 2:2.0.7-1

debian advisories DEBIAN-CVE-2018-12019

  • enigmail SLE Workstation Extension 15 2.0.7-3.7.2

suse advisories SUSE-SU-2018:2243-1

  • enigmail openSUSE Tumbleweed 2.2.4-1.4

opensuse advisories openSUSE-SU-2024:10736-1

Is CVE-2018-12019 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-12019 updated cvss 5.3

thunderbird-enigmail: Signature verification does not handle user ids correctly allowing attackers to spoof arbitrary email signatures

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.06% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • enigmail.net https://www.enigmail.net/index.php/en/download/changelog referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

Fencer Intel 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.