# CVE-2019-11730: Information disclosure in Firefox

> Attackers can read local files via file URIs when users open malicious HTML attachments, potentially exposing sensitive data from other applications.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 23 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-11730, GHSA-353x-8rf5-m26c, UBUNTU-CVE-2019-11730

## What is CVE-2019-11730?

CVE-2019-11730 is a medium-severity vulnerability in Debian Debian Linux, published on 23 Jul 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

A vulnerability exists where if a user opens a locally saved HTML file, this file can use file: URIs to access other files in the same directory or sub-directories if the names are known or guessed. The Fetch API can then be used to read the contents of any files stored in these directories and they may uploaded to a server. It was demonstrated that in combination with a popular Android messaging app, if a malicious HTML attachment is sent to a user and they opened that attachment in Firefox, due to that app's predictable pattern for locally-saved file names, it is possible to read attachments the victim received from other correspondents. This vulnerability affects Firefox ESR < 60.8, Firefox < 68, and Thunderbird < 60.8.

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

It affects 6 products.


Products: Debian Debian Linux, Mozilla Firefox, Mozilla Firefox Esr, Mozilla Thunderbird, Opensuse Leap, Suse Package Hub.

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

Upgrade to a fixed version.

## Is CVE-2019-11730 being exploited?

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

Public exploit code:

- https://github.com/lihuaiqiu/CVE-2019-11730 (github_poc): https://github.com/lihuaiqiu/CVE-2019-11730

## 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-2019-11730 and fix it if it is affected.

What it is: CVE-2019-11730 is a medium-severity vulnerability in Debian Debian Linux, published on 23 Jul 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-11730 in the wild and no public exploit code.

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-2019-11730/ (Markdown: https://insights.sbomify.com/CVE-2019-11730/index.md)
```

## Sources

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

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