CVE Vulnerabilities


Exposure of Sensitive Information to an Unauthorized Actor

Published: Apr 12, 2017 | Modified: Aug 16, 2017
CVSS 3.x
CVSS 2.x
1.9 LOW

A Win32k information disclosure vulnerability exists in Microsoft Windows when the win32k component improperly provides kernel information. An attacker who successfully exploited the vulnerability could obtain information to further compromise the user’s system, aka Win32k Information Disclosure Vulnerability.


The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Affected Software

Name Vendor Start Version End Version
Windows_10 Microsoft * *
Windows_10 Microsoft 1511 1511
Windows_10 Microsoft 1607 1607
Windows_10 Microsoft 1703 1703
Windows_7 Microsoft * *
Windows_8.1 Microsoft * *
Windows_rt_8.1 Microsoft * *
Windows_server_2008 Microsoft * *
Windows_server_2008 Microsoft r2 r2
Windows_server_2012 Microsoft * *
Windows_server_2012 Microsoft r2 r2
Windows_server_2016 Microsoft * *
Windows_vista Microsoft * *

Extended Description

There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:

Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:

Information exposures can occur in different ways:

It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.