Microsoft Windows Client/Server Run-time Subsystem (CSRSS) Multiple Vulnerabilities

Last Update Date: 13 Jul 2011 11:23 Release Date: 13 Jul 2011 5995 Views

RISK: Medium Risk

TYPE: Operating Systems - Windows OS

CSRSS Local EOP AllocConsole Vulnerability
An elevation of privilege vulnerability exists in Windows CSRSS due to the way that the CSRSS subsystem assigns memory for specific user transactions. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
CSRSS Local EOP SrvSetConsoleLocalEUDC Vulnerability
An elevation of privilege vulnerability exists in Windows CSRSS due to the way that the CSRSS subsystem assigns memory for specific user transactions. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights
CSRSS Local EOP SrvSetConsoleNumberOfCommand Vulnerability
An elevation of privilege vulnerability exists in Windows CSRSS due to the way that the CSRSS subsystem assigns memory for specific user transactions. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
CSRSS Local EOP SrvWriteConsoleOutput Vulnerability
An elevation of privilege vulnerability exists in Windows CSRSS due to the way that the CSRSS subsystem assigns memory for specific user transactions. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
CSRSS Local EOP SrvWriteConsoleOutputString Vulnerability
An elevation of privilege vulnerability exists in Windows CSRSS due to the way that the CSRSS subsystem assigns memory for specific user transactions. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.