# CVE-2016-3201: Information disclosure in n/a

> Remote attackers can obtain sensitive process memory information via a crafted PDF document in Windows and Edge.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **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:** 16 Jun 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cg42-27q5-rjhh

## What is CVE-2016-3201?

CVE-2016-3201 is a medium-severity vulnerability in Microsoft Edge, published on 16 Jun 2016. 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

Microsoft Windows 8.1, Windows Server 2012 Gold and R2, Windows 10 Gold and 1511, and Microsoft Edge allow remote attackers to obtain sensitive information from process memory via a crafted PDF document, aka "Windows PDF Information Disclosure Vulnerability," a different vulnerability than CVE-2016-3215.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2016-3201?

It affects 4 products.


Products: Microsoft Edge, Microsoft Windows 10, Microsoft Windows 8.1, Microsoft Windows Server 2012.

## How do I fix CVE-2016-3201?

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

## Is CVE-2016-3201 being exploited?

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

## 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-2017-0037](https://insights.sbomify.com/CVE-2017-0037/): Microsoft Edge and Internet Explorer Type Confusion (high 8.1, 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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-3201 and fix it if it is affected.

What it is: CVE-2016-3201 is a medium-severity vulnerability in Microsoft Edge, published on 16 Jun 2016. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-3201 in the wild and no public exploit code.

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

## Sources

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

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