# CVE-2017-0067: Memory corruption in Browser

> Remote code execution via memory corruption in Microsoft scripting engines allows attackers to execute arbitrary code with user privileges.

- **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:** 17 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-87jf-pgx6-356w

## What is CVE-2017-0067?

CVE-2017-0067 is a high-severity memory corruption vulnerability in Microsoft Edge, published on 17 Mar 2017. 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 affected Microsoft scripting engines render when handling objects in memory in Microsoft browsers. These vulnerabilities could corrupt memory in such a way that an attacker could execute arbitrary code in the context of the current user. An attacker who successfully exploited the vulnerability could gain the same user rights as the current user. If the current user is logged on with administrative user rights, an attacker who successfully exploited the vulnerability could take control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. This vulnerability is different from those described in CVE-2017-0010, CVE-2017-0015, CVE-2017-0032, CVE-2017-0035, CVE-2017-0070, CVE-2017-0071, CVE-2017-0094, CVE-2017-0131, CVE-2017-0132, CVE-2017-0133, CVE-2017-0134, CVE-2017-0136, CVE-2017-0137, CVE-2017-0138, CVE-2017-0141, CVE-2017-0150, and CVE-2017-0151.

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

## Which versions are affected by CVE-2017-0067?

It affects 1 product.


Products: Microsoft Edge.

## How do I fix CVE-2017-0067?

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

## Is CVE-2017-0067 being exploited?

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

## 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-2017-0067 and fix it if it is affected.

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

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

## Sources

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

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