# CVE-2018-0986: Memory corruption in Microsoft Exchange Server

> Remote attackers can execute arbitrary code by sending a specially crafted file to systems using the Microsoft Malware Protection Engine.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-v2gp-f824-rv7r

## What is CVE-2018-0986?

CVE-2018-0986 is a high-severity memory corruption vulnerability in Microsoft Exchange Server, published on 4 Apr 2018. 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 when the Microsoft Malware Protection Engine does not properly scan a specially crafted file, leading to memory corruption, aka "Microsoft Malware Protection Engine Remote Code Execution Vulnerability." This affects Windows Defender, Windows Intune Endpoint Protection, Microsoft Security Essentials, Microsoft System Center Endpoint Protection, Microsoft Exchange Server, Microsoft System Center, Microsoft Forefront Endpoint Protection.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2018-0986?

It affects 6 products.


Products: Microsoft Exchange Server, Microsoft Forefront Endpoint Protection 2010, Microsoft Intune Endpoint Protection, Microsoft Security Essentials, Microsoft System Center Endpoint Protection, Microsoft Windows Defender.

## How do I fix CVE-2018-0986?

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

## Is CVE-2018-0986 being exploited?

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

Public exploit code:

- Microsoft Windows Defender - 'mpengine.dll' Memory Corruption (exploitdb)

## Other vulnerabilities in Microsoft Exchange Server

- [CVE-2024-21410](https://insights.sbomify.com/CVE-2024-21410/): Microsoft Exchange Server Privilege Escalation (critical 9.8, exploited in the wild)
- [CVE-2021-34473](https://insights.sbomify.com/CVE-2021-34473/): Microsoft Exchange Server Remote Code Execution (critical 9.1, exploited in the wild)
- [CVE-2021-26855](https://insights.sbomify.com/CVE-2021-26855/): Microsoft Exchange Server Remote Code Execution (critical 9.1, exploited in the wild)
- [CVE-2021-34523](https://insights.sbomify.com/CVE-2021-34523/): Microsoft Exchange Server Privilege Escalation (critical 9.0, exploited in the wild)
- [CVE-2023-21529](https://insights.sbomify.com/CVE-2023-21529/): Microsoft Exchange Server Deserialization of Untrusted Data (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0986 and fix it if it is affected.

What it is: CVE-2018-0986 is a high-severity memory corruption vulnerability in Microsoft Exchange Server, published on 4 Apr 2018. 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-2018-0986 exists.

Affected product: Microsoft Exchange Server. 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-2018-0986/ (Markdown: https://insights.sbomify.com/CVE-2018-0986/index.md)
```

## Sources

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

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