# CVE-2013-1675: Mozilla Firefox Information Disclosure

> Remote attackers can read sensitive process memory via a crafted website due to uninitialized data structures in Firefox and Thunderbird.

- **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:** Yes, since 3 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 May 2013
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-7cv2-f4f9-vw96

## What is CVE-2013-1675?

CVE-2013-1675 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 16 May 2013. 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

Mozilla Firefox before 21.0, Firefox ESR 17.x before 17.0.6, Thunderbird before 17.0.6, and Thunderbird ESR 17.x before 17.0.6 do not properly initialize data structures for the nsDOMSVGZoomEvent::mPreviousScale and nsDOMSVGZoomEvent::mNewScale functions, which allows remote attackers to obtain sensitive information from process memory via a crafted web site.

Weakness: CWE-665 (Improper Initialization)

## Which versions are affected by CVE-2013-1675?

It affects 18 products.


Products: Canonical Ubuntu Linux, Debian Debian Linux, Mozilla Firefox, Mozilla Thunderbird, Mozilla Thunderbird Esr, Opensuse Opensuse, Redhat Enterprise Linux Desktop, Redhat Enterprise Linux Eus, Redhat Enterprise Linux for Ibm Z Systems, Redhat Enterprise Linux for Ibm Z Systems Eus, Redhat Enterprise Linux for Power Big Endian, Redhat Enterprise Linux for Power Big Endian Eus, Redhat Enterprise Linux for Scientific Computing, Redhat Enterprise Linux Server, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Eus From Rhui, Redhat Enterprise Linux Workstation, Redhat Gluster Storage Server for On-Premise.

## How do I fix CVE-2013-1675?

Upgrade to a fixed version. US federal agencies must fix it by 24 Mar 2022.

## Is CVE-2013-1675 being exploited?

Yes. Attackers have exploited CVE-2013-1675 in the wild since at least 3 Mar 2022.

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1675 and fix it if it is affected.

What it is: CVE-2013-1675 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 16 May 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2013-1675 in the wild since at least 3 Mar 2022.

Affected product: Canonical Ubuntu 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-2013-1675/ (Markdown: https://insights.sbomify.com/CVE-2013-1675/index.md)
```

## Sources

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

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