# CVE-2019-9810: Memory corruption in Firefox

> A buffer overflow in the Firefox JIT compiler allows attackers to execute arbitrary code via crafted JavaScript.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/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:** 26 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** DEBIAN-CVE-2019-9810, GHSA-j339-cxg8-wjf2, UBUNTU-CVE-2019-9810

## What is CVE-2019-9810?

CVE-2019-9810 is a high-severity memory corruption vulnerability in Mozilla Firefox, published on 26 Apr 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

Incorrect alias information in IonMonkey JIT compiler for Array.prototype.slice method may lead to missing bounds check and a buffer overflow. This vulnerability affects Firefox < 66.0.1, Firefox ESR < 60.6.1, and Thunderbird < 60.6.1.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 6 products.


Products: Mozilla Firefox, Mozilla Thunderbird, Redhat Enterprise Linux, Redhat Enterprise Linux Eus, Redhat Enterprise Linux Server Aus, Redhat Enterprise Linux Server Tus.

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

Upgrade to a fixed version.

## Is CVE-2019-9810 being exploited?

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

Public exploit code:

- Exploit for CVE-2019-9810 Firefox on Windows 64-bit. (github_poc): https://github.com/0vercl0k/CVE-2019-9810
- Array.prototype.slice wrong alias information. (github_poc): https://github.com/xuechiyaobai/CVE-2019-9810-PoC
- Firefox < 66.0.1 - 'Array.prototype.slice' Buffer Overflow (exploitdb)
- Mozilla FireFox (Windows 10 x64) - Full Chain Client Side Attack (exploitdb)

## Other vulnerabilities in Mozilla Firefox

- [CVE-2019-11708](https://insights.sbomify.com/CVE-2019-11708/): Mozilla Firefox and Thunderbird Sandbox Escape (critical 10.0, exploited in the wild)
- [CVE-2010-3765](https://insights.sbomify.com/CVE-2010-3765/): Mozilla Multiple Products Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2022-26486](https://insights.sbomify.com/CVE-2022-26486/): Mozilla Firefox Use-After-Free (critical 9.6, exploited in the wild)
- [CVE-2022-26485](https://insights.sbomify.com/CVE-2022-26485/): Mozilla Firefox Use-After-Free (high 8.8, exploited in the wild)
- [CVE-2019-11707](https://insights.sbomify.com/CVE-2019-11707/): Mozilla Firefox and Thunderbird Type Confusion (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-9810 is a high-severity memory corruption vulnerability in Mozilla Firefox, published on 26 Apr 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-9810 in the wild and no public exploit code.

Affected product: Mozilla Firefox. 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-9810/ (Markdown: https://insights.sbomify.com/CVE-2019-9810/index.md)
```

## Sources

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

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