# CVE-2016-7202: ChakraCore RCE Vulnerability

> Remote attackers can execute arbitrary code or cause denial of service via crafted websites exploiting memory corruption in Internet Explorer and Edge scripting engines.

- **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:** Yes
- **Published:** 10 Nov 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mmfq-r3rg-8r7w

## What is CVE-2016-7202?

CVE-2016-7202 is a high-severity memory corruption vulnerability in Microsoft Edge, published on 10 Nov 2016. 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

The scripting engines in Microsoft Internet Explorer 9 through 11 and Microsoft Edge allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Scripting Engine Memory Corruption Vulnerability," as demonstrated by the Chakra JavaScript engine, a different vulnerability than CVE-2016-7200, CVE-2016-7201, CVE-2016-7203, CVE-2016-7208, CVE-2016-7240, CVE-2016-7242, and CVE-2016-7243.

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

## Which versions are affected by CVE-2016-7202?

2 open source packages ship an affected version, including Microsoft.ChakraCore. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Microsoft.ChakraCore` | NuGet | All versions | 1.2.2 |
| `Microsoft.ChakraCore` | NuGet | All versions | 1.2.2 |

Products: Microsoft Edge.

## How do I fix CVE-2016-7202?

Upgrade Microsoft.ChakraCore to 1.2.2 or later.

## Is CVE-2016-7202 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-7202 exists.

Public exploit code:

- Microsoft Edge - 'Array.reverse' Overflow (exploitdb)
- Microsoft Edge Scripting Engine - Memory Corruption (MS16-129) (exploitdb)

## Other vulnerabilities in Microsoft Edge

- [CVE-2021-26411](https://insights.sbomify.com/CVE-2021-26411/): Microsoft Internet Explorer Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2016-7200](https://insights.sbomify.com/CVE-2016-7200/): Microsoft Edge Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2016-7201](https://insights.sbomify.com/CVE-2016-7201/): Microsoft Edge Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2017-0037](https://insights.sbomify.com/CVE-2017-0037/): Microsoft Edge and Internet Explorer Type Confusion (high 8.1, exploited in the wild)
- [CVE-2016-3351](https://insights.sbomify.com/CVE-2016-3351/): Microsoft Internet Explorer and Edge Information Disclosure (medium 6.5, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-7202 and fix it if it is affected.

What it is: CVE-2016-7202 is a high-severity memory corruption vulnerability in Microsoft Edge, published on 10 Nov 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-7202 exists.

Affected packages and fixed versions:
- Microsoft.ChakraCore (NuGet): affected all versions; fixed in 1.2.2
- Microsoft.ChakraCore (NuGet): affected all versions; fixed in 1.2.2

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

## Sources

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

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