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

> Mailpile's encryption feature fails to exclude disabled or expired keys, allowing potential use of invalid keys for security operations.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rfvw-9494-24h7

## What is CVE-2018-20954?

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

### Official description

The "Security and Privacy" Encryption feature in Mailpile before 1.0.0rc4 does not exclude disabled, revoked, and expired keys.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Mailpile Mailpile.

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

No fix has been published for CVE-2018-20954 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-20954 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-20954 is a high-severity vulnerability in n/a, published on 8 Aug 2019. 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-20954 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-20954/ (Markdown: https://insights.sbomify.com/CVE-2018-20954/index.md)
```

## Sources

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

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