# CVE-2019-13075: Information disclosure in n/a

> Remote attackers can detect the browser's language setting via IFRAME elements, exposing user configuration details.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 30 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-13075, GHSA-399p-gmjm-mpxv

## What is CVE-2019-13075?

CVE-2019-13075 is a medium-severity vulnerability in n/a, published on 30 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tor Browser through 8.5.3 has an information exposure vulnerability. It allows remote attackers to detect the browser's language via vectors involving an IFRAME element, because text in that language is included in the title attribute of a LINK element for a non-HTML page. This is related to a behavior of Firefox before 68.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Torproject Tor Browser.

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

Upgrade to a fixed version.

## Is CVE-2019-13075 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-39246](https://insights.sbomify.com/CVE-2021-39246/): Information disclosure in n/a (medium 6.1)
- [CVE-2019-12383](https://insights.sbomify.com/CVE-2019-12383/): Information disclosure in n/a (medium 4.3)
- [CVE-2017-16639](https://insights.sbomify.com/CVE-2017-16639/): Information disclosure in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13075 and fix it if it is affected.

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

## Sources

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

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