# CVE-2017-0290: Memory corruption in Microsoft Malware Protection Engine

> Attacker can execute arbitrary code by tricking the Windows Malware Protection Engine into scanning a specially crafted file.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-w3hq-vf6w-p52j

## What is CVE-2017-0290?

CVE-2017-0290 is a high-severity memory corruption vulnerability in Microsoft Malware Protection Engine, published on 9 May 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The Microsoft Malware Protection Engine running on Microsoft Forefront and Microsoft Defender on Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, 1607, and 1703, and Windows Server 2016 does not properly scan a specially crafted file leading to memory corruption, aka "Microsoft Malware Protection Engine Remote Code Execution Vulnerability."

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

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

It affects 3 products.


Products: Microsoft Forefront Security, Microsoft Malware Protection Engine, Microsoft Windows Defender.

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

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

## Is CVE-2017-0290 being exploited?

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

Public exploit code:

- Microsoft Security Essentials / SCEP (Microsoft Windows 8/8.1/10 / Windows Server) - 'MsMpEng' Remote Type Confusion (exploitdb)
- https://github.com/homjxi0e/CVE-2017-0290- (github_poc): https://github.com/homjxi0e/CVE-2017-0290-

## Other vulnerabilities in Microsoft Malware Protection Engine

- [CVE-2017-8538](https://insights.sbomify.com/CVE-2017-8538/): Memory corruption in Malware Protection Engine (high 7.8)
- [CVE-2017-8541](https://insights.sbomify.com/CVE-2017-8541/): Memory corruption in Malware Protection Engine (high 7.8)
- [CVE-2017-8539](https://insights.sbomify.com/CVE-2017-8539/): Denial of service in Malware Protection Engine (medium 5.5)
- [CVE-2017-8542](https://insights.sbomify.com/CVE-2017-8542/): Denial of service in Malware Protection (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-0290 is a high-severity memory corruption vulnerability in Microsoft Malware Protection Engine, published on 9 May 2017. It can only be exploited from the same machine or local network, 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-2017-0290 exists.

Affected product: Microsoft Malware Protection Engine. 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-0290/ (Markdown: https://insights.sbomify.com/CVE-2017-0290/index.md)
```

## Sources

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

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