# CVE-2019-10741: Other in n/a

> Attackers can forge valid S/MIME or PGP signatures for arbitrary content by exploiting HTML rendering differences in K-9 Mail replies.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-p93q-2cgh-jc3x

## What is CVE-2019-10741?

CVE-2019-10741 is a medium-severity vulnerability in n/a, published on 7 Apr 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

K-9 Mail v5.600 can include the original quoted HTML code of a specially crafted, benign looking, email within (digitally signed) reply messages. The quoted part can contain conditional statements that show completely different text if opened in a different email client. This can be abused by an attacker to obtain valid S/MIME or PGP signatures for arbitrary content to be displayed to a third party. NOTE: the vendor states "We don't plan to take any action because of this."

Weakness: CWE-254

## Which versions are affected by CVE-2019-10741?

It affects 1 product.


Products: K-9 Mail Project K-9 Mail.

## How do I fix CVE-2019-10741?

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

## Is CVE-2019-10741 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-10741 and fix it if it is affected.

What it is: CVE-2019-10741 is a medium-severity vulnerability in n/a, published on 7 Apr 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-10741 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-2019-10741/ (Markdown: https://insights.sbomify.com/CVE-2019-10741/index.md)
```

## Sources

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

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