# CVE-2016-7287: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service via crafted websites exploiting memory corruption in Microsoft browsers.

- **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:** 20 Dec 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7fvc-39jg-hx7f

## What is CVE-2016-7287?

CVE-2016-7287 is a high-severity memory corruption vulnerability in Microsoft Edge, published on 20 Dec 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 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."

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

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

It affects 2 products.


Products: Microsoft Edge, Microsoft Internet Explorer.

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

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

## Is CVE-2016-7287 being exploited?

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

Public exploit code:

- Microsoft Edge - Internationalization Initialization Type Confusion (MS16-144) (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-7287 and fix it if it is affected.

What it is: CVE-2016-7287 is a high-severity memory corruption vulnerability in Microsoft Edge, published on 20 Dec 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-7287 exists.

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

## Sources

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

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