# CVE-2024-1936: Information disclosure in Thunderbird

> An attacker can cause email subject leakage to third parties via cache contamination in Thunderbird, requiring users to upgrade and repair folders.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** Yes
- **Published:** 4 Mar 2024
- **Updated:** 26 Nov 2024
- **Also known as:** DEBIAN-CVE-2024-1936, GHSA-8v87-67f4-56h2, MGASA-2024-0054, SUSE-SU-2024:0893-1, UBUNTU-CVE-2024-1936, openSUSE-SU-2024:13753-1

## What is CVE-2024-1936?

CVE-2024-1936 is a high-severity vulnerability in Debian Debian Linux, published on 4 Mar 2024. 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

The encrypted subject of an email message could be incorrectly and permanently assigned to an arbitrary other email message in Thunderbird's local cache. Consequently, when replying to the contaminated email message, the user might accidentally leak the confidential subject to a third-party. While this update fixes the bug and avoids future message contamination, it does not automatically repair existing contaminations. Users are advised to use the repair folder functionality, which is available from the context menu of email folders, which will erase incorrect subject assignments. This vulnerability affects Thunderbird < 115.8.1.

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `MozillaThunderbird` | SUSE:Linux Enterprise Module for Package Hub 15 SP5 | All versions | 115.8.1-150200.8.151.1 |
| `MozillaThunderbird` | SUSE:Linux Enterprise Workstation Extension 15 SP5 | All versions | 115.8.1-150200.8.151.1 |
| `MozillaThunderbird` | openSUSE:Leap 15.5 | All versions | 115.8.1-150200.8.151.1 |
| `MozillaThunderbird` | openSUSE:Tumbleweed | All versions | 115.8.1-1.1 |

Products: Debian Debian Linux, Mozilla Thunderbird.

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

Upgrade to a fixed version.

## Is CVE-2024-1936 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1936 exists.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1936 is a high-severity vulnerability in Debian Debian Linux, published on 4 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1936 exists.

Affected product: Debian Debian Linux. 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-1936/ (Markdown: https://insights.sbomify.com/CVE-2024-1936/index.md)
```

## Sources

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

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