# CVE-2017-9604: Information disclosure in n/a

> Attackers can sniff network traffic to obtain sensitive information because KMail fails to encrypt messages when using the Send Later feature.

- **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:** Yes
- **Published:** 13 Jun 2017
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2017-9604, GHSA-7w32-mxrp-49jg, UBUNTU-CVE-2017-9604, openSUSE-SU-2017:1748-1, openSUSE-SU-2017:1756-1

## What is CVE-2017-9604?

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

### Official description

KDE kmail before 5.5.2 and messagelib before 5.5.2, as distributed in KDE Applications before 17.04.2, do not ensure that a plugin's sign/encrypt action occurs during use of the Send Later feature, which allows remote attackers to obtain sensitive information by sniffing the network.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

## Which versions are affected by CVE-2017-9604?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kdepim` | SUSE:Package Hub 12 SP2 | All versions | 16.08.2-5.2 |
| `kdepim` | SUSE:Package Hub 12 SP2 | All versions | 16.08.2-5.2 |
| `messagelib` | SUSE:Package Hub 12 SP2 | All versions | 16.08.2-5.1 |
| `messagelib` | SUSE:Package Hub 12 SP2 | All versions | 16.08.2-5.1 |

Products: Kde Kmail, Kde Messagelib.

## How do I fix CVE-2017-9604?

Upgrade to a fixed version.

## Is CVE-2017-9604 being exploited?

There is no known exploitation of CVE-2017-9604 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-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-2014-8878](https://insights.sbomify.com/CVE-2014-8878/): Weak cryptography in n/a (medium 5.9)
- [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-2017-9604 and fix it if it is affected.

What it is: CVE-2017-9604 is a high-severity vulnerability in n/a, published on 13 Jun 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-2017-9604 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-2017-9604/ (Markdown: https://insights.sbomify.com/CVE-2017-9604/index.md)
```

## Sources

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

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