# CVE-2017-8487: Code injection in Microsoft Windows

> Attackers can execute arbitrary code by tricking users into opening malicious files via Windows OLE, requiring immediate patching.

- **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:** 15 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-84p6-78m2-238m

## What is CVE-2017-8487?

CVE-2017-8487 is a high-severity code injection vulnerability in Microsoft Windows Server 2003, published on 15 Jun 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

Windows OLE in Windows XP and Windows Server 2003 allows an attacker to execute code when a victim opens a specially crafted file or program aka "Windows olecnv32.dll Remote Code Execution Vulnerability."

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

It affects 2 products.


Products: Microsoft Windows Server 2003, Microsoft Windows Xp.

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

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

## Is CVE-2017-8487 being exploited?

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

Public exploit code:

- Microsoft Windows - 'IOCTL 0x390400_ operation code 0x00020000' Kernel KsecDD Pool Memory Disclosure (exploitdb)

## Other vulnerabilities in Microsoft Windows Server 2003

- [CVE-2011-2005](https://insights.sbomify.com/CVE-2011-2005/): Microsoft Ancillary Function Driver (afd.sys) Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2013-3863](https://insights.sbomify.com/CVE-2013-3863/): Memory corruption in n/a (critical 9.3)
- [CVE-2013-3181](https://insights.sbomify.com/CVE-2013-3181/): Memory corruption in n/a (critical 9.3)
- [CVE-2013-0077](https://insights.sbomify.com/CVE-2013-0077/): Code injection in n/a (critical 9.3)
- [CVE-2012-0009](https://insights.sbomify.com/CVE-2012-0009/): Path traversal in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8487 is a high-severity code injection vulnerability in Microsoft Windows Server 2003, published on 15 Jun 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-8487 exists.

Affected product: Microsoft Windows Server 2003. 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-8487/ (Markdown: https://insights.sbomify.com/CVE-2017-8487/index.md)
```

## Sources

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

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