# CVE-2024-50624: Other in n/a

> Man-in-the-middle attackers can redirect mail configuration requests to malicious servers due to cleartext HTTP usage in KDE Kmail.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Oct 2024
- **Updated:** 31 May 2025
- **Also known as:** DEBIAN-CVE-2024-50624, DLA-4196-1, GHSA-wvrr-8f7c-7346, UBUNTU-CVE-2024-50624, USN-7732-1, openSUSE-SU-2024:0353-1

## What is CVE-2024-50624?

CVE-2024-50624 is a medium-severity vulnerability in n/a, published on 27 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ispdbservice.cpp in KDE Kmail before 6.2.0 allows man-in-the-middle attackers to trigger use of an attacker-controlled mail server because cleartext HTTP is used for a URL such as http://autoconfig.example.com or http://example.com/.well-known/autoconfig for retrieving the configuration. This is related to kmail-account-wizard.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2024-50624?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kmail-account-wizard` | SUSE:Package Hub 15 SP5 | All versions | 23.08.5-bp156.2.3.1 |
| `kmail-account-wizard` | SUSE:Package Hub 15 SP6 | All versions | 23.08.5-bp156.2.3.1 |
| `kmail-account-wizard` | openSUSE:Leap 15.5 | All versions | 23.08.5-bp156.2.3.1 |
| `kmail-account-wizard` | openSUSE:Leap 15.6 | All versions | 23.08.5-bp156.2.3.1 |

## How do I fix CVE-2024-50624?

Upgrade to a fixed version.

## Is CVE-2024-50624 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50624 and fix it if it is affected.

What it is: CVE-2024-50624 is a medium-severity vulnerability in n/a, published on 27 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-50624 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-2024-50624/ (Markdown: https://insights.sbomify.com/CVE-2024-50624/index.md)
```

## Sources

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

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