# CVE-2018-12019: Security feature bypass in n/a

> Remote attackers can spoof arbitrary email signatures by exploiting flawed signature verification logic in Enigmail, undermining email authenticity.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-12019, GHSA-fc79-j7vw-6xjg, UBUNTU-CVE-2018-12019

## What is CVE-2018-12019?

CVE-2018-12019 is a high-severity vulnerability in n/a, published on 13 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2018-12019?

It affects 1 product.


Products: Enigmail Enigmail.

## How do I fix CVE-2018-12019?

Upgrade to a fixed version.

## Is CVE-2018-12019 being exploited?

There is no known exploitation of CVE-2018-12019 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2006-5877](https://insights.sbomify.com/CVE-2006-5877/): Denial of service in n/a (high 7.8)
- [CVE-2019-12269](https://insights.sbomify.com/CVE-2019-12269/): Other in n/a (high 7.5)
- [CVE-2019-14664](https://insights.sbomify.com/CVE-2019-14664/): Information disclosure in n/a (medium 6.5)
- [CVE-2018-15586](https://insights.sbomify.com/CVE-2018-15586/): Security feature bypass in n/a (medium 6.5)
- [CVE-2007-1264](https://insights.sbomify.com/CVE-2007-1264/): Security feature bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-12019 and fix it if it is affected.

What it is: CVE-2018-12019 is a high-severity vulnerability in n/a, published on 13 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-12019 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-12019/ (Markdown: https://insights.sbomify.com/CVE-2018-12019/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-12019
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-12019
- OSV: https://osv.dev/vulnerability/CVE-2018-12019

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-12019/
Summaries are generated and may contain mistakes; the official description above is the record.