# CVE-2019-0605: Memory corruption in ChakraCore

> A memory corruption vulnerability in Microsoft Edge's scripting engine allows remote attackers to execute arbitrary code.

- **Severity:** High 7.5 (`CVSS:3.0/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:** No
- **Published:** 6 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r534-43c2-gm8w

## What is CVE-2019-0605?

CVE-2019-0605 is a high-severity memory corruption vulnerability in Microsoft Chakracore, published on 6 Mar 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 remote code execution vulnerability exists in the way that the scripting engine handles objects in memory in Microsoft Edge, aka 'Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0590, CVE-2019-0591, CVE-2019-0593, CVE-2019-0607, CVE-2019-0610, CVE-2019-0640, CVE-2019-0642, CVE-2019-0644, CVE-2019-0651, CVE-2019-0652, CVE-2019-0655.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 2 products.


Products: Microsoft Chakracore, Microsoft Edge.

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

No fix has been published for CVE-2019-0605 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-0605 being exploited?

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

## Other vulnerabilities in Microsoft Chakracore

- [CVE-2018-8298](https://insights.sbomify.com/CVE-2018-8298/): ChakraCore Scripting Engine Type Confusion (high 7.5, exploited in the wild)
- [CVE-2020-0878](https://insights.sbomify.com/CVE-2020-0878/): Microsoft Edge and Internet Explorer Memory Corruption (medium 4.2, exploited in the wild)
- [CVE-2018-8500](https://insights.sbomify.com/CVE-2018-8500/): ChakraCore RCE Vulnerability (critical 9.8)
- [CVE-2017-11767](https://insights.sbomify.com/CVE-2017-11767/): ChakraCore vulnerable to privilege escalation (critical 9.8)
- [CVE-2017-8658](https://insights.sbomify.com/CVE-2017-8658/): ChakraCore RCE Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-0605 is a high-severity memory corruption vulnerability in Microsoft Chakracore, published on 6 Mar 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-0605 in the wild and no public exploit code.

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

## Sources

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

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