|
|
|
|
| |
Credit:
The information has been provided by Microsoft Product Security.
The original article can be found at: http://www.microsoft.com/technet/security/Bulletin/MS08-025.mspx
|
| |
Affected Software:
Operating System - Maximum Security Impact - Aggregate Severity Rating - Bulletins Replaced by this Update
* Microsoft Windows 2000 Service Pack 4 - Elevation of Privilege - Important - None
* Windows XP Service Pack 2 - Elevation of Privilege - Important - None
* Windows XP Professional x64 Edition and Windows XP Professional x64 Edition Service Pack 2 - Elevation of Privilege - Important - None
* Windows Server 2003 Service Pack 1 and Windows Server 2003 Service Pack 2 - Elevation of Privilege - Important - None
* Windows Server 2003 x64 Edition and Windows Server 2003 x64 Edition Service Pack 2 - Elevation of Privilege - Important - None
* Windows Server 2003 with SP1 for Itanium-based Systems and Windows Server 2003 with SP2 for Itanium based Systems - Elevation of Privilege - Important - None
* Windows Vista and Windows Vista Service Pack 1 - Elevation of Privilege - Important - None
* Windows Vista x64 Edition and Windows Vista x64 Edition Service Pack 1 - Elevation of Privilege - Important - None
* Windows Server 2008 for 32-bit Systems - Elevation of Privilege - Important - None
* Windows Server 2008 for x64-based Systems - Elevation of Privilege - Important - None
* Windows Server 2008 for Itanium-based Systems - Elevation of Privilege - Important - None
Windows Kernel Vulnerability - CVE-2008-1084
An elevation of privilege vulnerability exists due to the Windows kernel improperly validating input passed from user mode to the kernel. The vulnerability could allow an attacker to run code with elevated privileges. An attacker who successfully exploited this vulnerability could execute arbitrary code and take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
CVE Information:
CVE-2008-1084
Mitigating Factors for Windows Kernel Vulnerability - CVE-2008-1084
An attacker must have valid logon credentials and be able to log on locally to a vulnerable system in order to exploit this vulnerability. The vulnerability could not be exploited remotely or by anonymous users.
FAQ for Windows Kernel Vulnerability - CVE-2008-1084
What is the scope of the vulnerability?
This is an elevation of privilege vulnerability. An attacker who successfully exploited this vulnerability could execute arbitrary code and take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.
What causes the vulnerability?
The Windows kernel improperly validating input passed from user mode to the Kernel.
What is the Windows kernel?
The Windows kernel is the core of the operating system. It provides system level services such as device management and memory management, it allocates processor time to processes, and it manages error handling.
What might an attacker use the vulnerability to do?
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.
How could an attacker exploit the vulnerability?
To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take complete control over the affected system.
What systems are primarily at risk from the vulnerability?
Any Windows system that allowed potentially hostile users to log on locally could be at risk from this vulnerability. Windows XP Service Pack 3 is not affected by this Vulnerability.
What does the update do?
The update removes the vulnerability by correctly validating parameters passed to the Windows Kernel by user mode callbacks.
When this security bulletin was issued, had this vulnerability been publicly disclosed?
No. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.
When this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.
|
|
|
|
|
