# CVE-2020-1487: Media Foundation Information Disclosure Vulnerability

> An attacker can obtain sensitive information by tricking a user into opening a specially crafted file, aiding further system compromise.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gf86-frf5-frmh

## What is CVE-2020-1487?

CVE-2020-1487 is a high-severity vulnerability in Microsoft Windows 10, published on 17 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An information disclosure vulnerability exists when Media Foundation improperly handles objects in memory. An attacker who successfully exploited this vulnerability could obtain information to further compromise the user’s system.
To exploit this vulnerability, an attacker would have to log onto an affected system and open a specially crafted file. In a web-based attack scenario, an attacker could host a website (or leverage a compromised website that accepts or hosts user-provided content) that contains a specially crafted file that is designed to exploit the vulnerability. However, an attacker would have no way to force the user to visit the website. Instead, an attacker would have to convince the user to click a link, typically by way of an enticement in an email or Instant Messenger message, and then convince the user to open the specially crafted file.
The update addresses the vulnerability by correcting how Media Foundation handles objects in memory.

## Which versions are affected by CVE-2020-1487?

It affects 6 products.


Products: Microsoft Windows 10, Microsoft Windows 8.1, Microsoft Windows Rt 8.1, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019.

## How do I fix CVE-2020-1487?

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

## Is CVE-2020-1487 being exploited?

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

## Other vulnerabilities in Microsoft Windows 10

- [CVE-2015-2426](https://insights.sbomify.com/CVE-2015-2426/): Microsoft Windows Adobe Type Manager Library Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2015-1769](https://insights.sbomify.com/CVE-2015-1769/): Microsoft Windows Mount Manager Privilege Escalation (medium 6.6, exploited in the wild)
- [CVE-2020-1467](https://insights.sbomify.com/CVE-2020-1467/): Windows Hard Link Elevation of Privilege Vulnerability (critical 10.0)
- [CVE-2021-26424](https://insights.sbomify.com/CVE-2021-26424/): Windows TCP/IP Remote Code Execution Vulnerability (critical 9.9)
- [CVE-2021-28476](https://insights.sbomify.com/CVE-2021-28476/): Windows Hyper-V Remote Code Execution Vulnerability (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1487 and fix it if it is affected.

What it is: CVE-2020-1487 is a high-severity vulnerability in Microsoft Windows 10, published on 17 Aug 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-1487 in the wild and no public exploit code.

Affected product: Microsoft Windows 10. 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-2020-1487/ (Markdown: https://insights.sbomify.com/CVE-2020-1487/index.md)
```

## Sources

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

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