# CVE-2017-11831: Information disclosure in Windows kernel

> An attacker can exploit a Windows kernel memory initialization flaw to disclose information and potentially escalate privileges on affected systems.

- **Severity:** Medium 4.7 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 15 Nov 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-93fq-ggx4-97cm

## What is CVE-2017-11831?

CVE-2017-11831 is a medium-severity vulnerability in Microsoft Windows 10, published on 15 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Windows kernel in Windows 7 SP1, Windows 8.1 and RT 8.1, Windows Server 2008 SP2 and R2 SP1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, 1703, 1709, Windows Server 2016, and Windows Server, version 1709 allows an attacker to log on to an affected system, and run a specially crafted application that can compromise the user's system due to how the Windows kernel initializes memory, aka "Windows Information Disclosure Vulnerability". This CVE ID is unique from CVE-2017-11880.

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

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

It affects 8 products.


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

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

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

## Is CVE-2017-11831 being exploited?

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

Public exploit code:

- Microsoft Windows 10 - 'nt!NtQueryDirectoryFile (luafv!LuafvCopyDirectoryEntry)' Pool Memory Disclosure (exploitdb)

## 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-2017-11831 and fix it if it is affected.

What it is: CVE-2017-11831 is a medium-severity vulnerability in Microsoft Windows 10, published on 15 Nov 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-11831 exists.

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

## Sources

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

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