# CVE-2014-8878: Weak cryptography in n/a

> KDE KMail fails to encrypt attachments when automatic encryption is enabled, allowing attackers to sniff sensitive data from network traffic.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/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:** Yes
- **Published:** 27 Sep 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-67gw-pr7f-99hr, MGASA-2015-0315, UBUNTU-CVE-2014-8878

## What is CVE-2014-8878?

CVE-2014-8878 is a medium-severity vulnerability in n/a, published on 27 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

KDE KMail does not encrypt attachments in emails when "automatic encryption" is enabled, which allows remote attackers to obtain sensitive information by sniffing the network.

Weakness: CWE-310

## Which versions are affected by CVE-2014-8878?

It affects 1 product.


Products: Kde Kmail.

## How do I fix CVE-2014-8878?

Apply the vendor's patch.

## Is CVE-2014-8878 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-7967](https://insights.sbomify.com/CVE-2016-7967/): Code injection in n/a (high 8.1)
- [CVE-2017-9604](https://insights.sbomify.com/CVE-2017-9604/): Information disclosure in n/a (high 7.5)
- [CVE-2020-11880](https://insights.sbomify.com/CVE-2020-11880/): Path traversal in n/a (medium 6.5)
- [CVE-2016-7968](https://insights.sbomify.com/CVE-2016-7968/): Cross-site scripting in n/a (medium 6.5)
- [CVE-2021-38373](https://insights.sbomify.com/CVE-2021-38373/): Security feature bypass in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-8878 and fix it if it is affected.

What it is: CVE-2014-8878 is a medium-severity vulnerability in n/a, published on 27 Sep 2017. 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-2014-8878 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-2014-8878/ (Markdown: https://insights.sbomify.com/CVE-2014-8878/index.md)
```

## Sources

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

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