Liang Yin

**Name of the Vulnerable Software and Affected Versions** The product name cannot be determined. **Description** An elevation-of-privilege issue allows attackers to affect the system. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Microsoft Windows versions 8.1 through 10 (including Windows RT 8.1, Windows Server 2012 R2, Windows Server 2016, and versions 1511, 1607, 1703) **Description** The issue is related to the improper handling of data in device memory by the Windows kernel, allowing a local attacker to execute code in the context of a privileged process. This can enable an attacker to run processes in an elevated context. The vulnerability is also described as an elevation-of-privilege issue that affects the system. **Recommendations** For Microsoft Windows versions 8.1 through 10, update to a version that includes the fix for this issue to prevent exploitation. For Windows Server 2012 R2 and Windows Server 2016, apply the necessary patch or update to resolve the vulnerability. At the moment, there is no information about a newer version that contains a fix for this vulnerability for other affected versions, so ensure to monitor for updates from Microsoft.

**Name of the Vulnerable Software and Affected Versions** Microsoft Windows XP versions SP2 through SP3 Microsoft Windows Server 2003 version SP2 **Description** An issue exists in the way the Windows Client/Server Run-time Subsystem (CSRSS) terminates a process when a user logs off, allowing local users to obtain sensitive information or gain privileges via a crafted application. This could enable an attacker to monitor the actions of a subsequent user, potentially disclosing sensitive information or accessing data that was accessible to the logged-on user, including logon credentials. If a user with administrative privileges logs on, the attacker could run arbitrary code in kernel mode. **Recommendations** For Microsoft Windows XP versions SP2 through SP3, update to a version that includes the fix for this issue. For Microsoft Windows Server 2003 version SP2, update to a version that includes the fix for this issue. As a temporary workaround, consider restricting access to sensitive data and limiting user privileges to minimize the risk of exploitation.