# CVE-2017-0037: Microsoft Edge and Internet Explorer Type Confusion

> Remote attackers can execute arbitrary code in Internet Explorer and Edge via crafted CSS and JavaScript exploiting a type confusion vulnerability.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 28 Mar 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Feb 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-xpg5-jv85-754h

## What is CVE-2017-0037?

CVE-2017-0037 is a high-severity memory corruption vulnerability in Microsoft Edge, published on 26 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Microsoft Internet Explorer 10 and 11 and Microsoft Edge have a type confusion issue in the Layout::MultiColumnBoxBuilder::HandleColumnBreakOnColumnSpanningElement function in mshtml.dll, which allows remote attackers to execute arbitrary code via vectors involving a crafted Cascading Style Sheets (CSS) token sequence and crafted JavaScript code that operates on a TH element.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

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

It affects 2 products.


Products: Microsoft Edge, Microsoft Internet Explorer.

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

No fix has been published for CVE-2017-0037 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 18 Apr 2022.

## Is CVE-2017-0037 being exploited?

Yes. Attackers have exploited CVE-2017-0037 in the wild since at least 28 Mar 2022.

Public exploit code:

- Microsoft Edge / Internet Explorer - 'HandleColumnBreakOnColumnSpanningElement' Type Confusion (exploitdb)
- Microsoft Internet Explorer - 'mshtml.dll' Remote Code Execution (MS17-007) (exploitdb)
- Microsoft Internet Explorer 11 (Windows 7 x86) - 'mshtml.dll' Remote Code Execution (MS17-007) (exploitdb)
- https://github.com/chattopadhyaykittu/CVE-2017-0037 (github_poc): https://github.com/chattopadhyaykittu/CVE-2017-0037

## 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-2016-3351](https://insights.sbomify.com/CVE-2016-3351/): Microsoft Internet Explorer and Edge Information Disclosure (medium 6.5, exploited in the wild)
- [CVE-2017-0028](https://insights.sbomify.com/CVE-2017-0028/): Memory corruption in Microsoft ChakraCore (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-0037 and fix it if it is affected.

What it is: CVE-2017-0037 is a high-severity memory corruption vulnerability in Microsoft Edge, published on 26 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2017-0037 in the wild since at least 28 Mar 2022.

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

## Sources

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

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