Microsoft Windows XP 'i2omgmt.sys' Input Validation Flaw Lets Local Users Gain Elevated Privileges
SecurityTracker Alert ID: 1020006|
SecurityTracker URL: http://securitytracker.com/id/1020006
(Links to External Site)
Date: May 12 2008
Root access via local system|
Fix Available: Yes Vendor Confirmed: Yes |
Version(s): XP SP2 and prior service packs|
A vulnerability was reported in Windows XP. A local user can obtain kernel level privileges on the target system.|
A local user can access the \\.\I2OExc interface of the Intelligent Input/Output (I2O) Utility Filter driver (i2omgmt.sys) and supply a specially crafted DeviceObject pointer value to execute arbitrary code on the target system with kernel privileges.
The vendor was notified on March 20, 2007.
Ruben Santamarta of reversemode.com reported this vulnerability via iDefense.
A local user can obtain kernel level privileges on the target system.|
Microsoft has issued a fix (XP SP3).|
The Microsoft advisory is available at:
Vendor URL: www.microsoft.com/downloads/details.aspx?FamilyID=5b33b5a8-5e76-401f-be08-1e1555d4f3d4 (Links to External Site)
Access control error|
Source Message Contents
Subject: iDefense Security Advisory 05.12.08: Microsoft Windows I2O Filter|
iDefense Security Advisory 05.12.08
May 12, 2008
Intelligent Input/Output (I2O) is a defunct computer input/output (I/O)
specification. i2omgmt.sys is a Windows driver for the I2O Utility
Filter. For more background information about I2O, see following
Local exploitation of an input validation vulnerability within version
5.1.2600.2180 of i2omgmt.sys, as included with Microsoft Corp's Windows
XP operating system, could allow an attacker to execute arbitrary code
in the context of the kernel.
This vulnerability specifically exists due to insecure permissions on
the \\.\I2OExc device interface. The permissions on this device allow
"Everyone" write access. This could allow a locally logged-in user to
access functionality designed for privileged use only.
Additionally, the IOCTL handlers for this device interface do not
properly validate user-mode buffer passed to them, so an attacker can
supply a fake DeviceObject pointer to a user-mode address. As such, it
is possible to overwrite arbitrary memory or execute attacker-supplied
code in the context of the kernel.
Exploitation allows an attacker to elevate privileges by overwriting
arbitrary system memory or executing code within kernel context. An
attacker needs to log-in to the target machine to exploit this
This driver is related to I2O protocol and RAID devices. It is not
present by default on every Windows installation. However, iDefense
found this driver loaded on several systems we tested.
iDefense has confirmed the existence of this vulnerability in
i2omgmt.sys version 5.1.2600.2180 as installed on some Windows XP SP2
systems. All other Windows releases with this driver, including
previous versions, are suspected to be vulnerable.
Removing write permissions for "Everyone" appears to prevent access to
the vulnerable code. Although no side effects were witnessed in lab
tests, normal functionality may be hindered.
VI. VENDOR RESPONSE
Microsoft has addressed this issue within Windows XP Service Pack 3. To
obtain Microsoft XP Service Pack 3, visit the following URL.
VII. CVE INFORMATION
The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CVE-2008-0322 to this issue. This is a candidate for inclusion in
the CVE list (http://cve.mitre.org/), which standardizes names for
VIII. DISCLOSURE TIMELINE
03/20/2007 Initial vendor notification
03/20/2007 Initial vendor response
05/12/2008 Coordinated public disclosure
Get paid for vulnerability research
Free tools, research and upcoming events
X. LEGAL NOTICES
Permission is granted for the redistribution of this alert
electronically. It may not be edited in any way without the express
written consent of iDefense. If you wish to reprint the whole or any
part of this alert in any other medium other than electronically,
please e-mail firstname.lastname@example.org for permission.
Disclaimer: The information in the advisory is believed to be accurate
at the time of publishing based on currently available information. Use
of the information constitutes acceptance for use in an AS IS condition.
There are no warranties with regard to this information. Neither the
author nor the publisher accepts any liability for any direct,
indirect, or consequential loss or damage arising from use of, or
reliance on, this information.
To unsubscribe, go here: