The Trend Micro AntiVirus scan engine is widely relied upon to provide AntiVirus capabilities to desktop, server, and gateway systems. The engine is licensed to several of Trend Micro's OEM partners. More information is available on Trend Micro's web site at the following URL.
Local exploitation of an input validation vulnerability within version 188.8.131.522 of TmComm.sys as included with Trend Micro's AntiVirus engine could allow an attacker execute arbitrary code in kernel context.
This vulnerability specifically exists due to insecure permissions on the \.TmComm DOS device interface. The permissions on this device allows "Everyone" write access. This could allow a locally logged in user to access functionality via IOCTLs which was designed for privileged use only.
Additionally, the IOCTL handlers for this DOS device interface do not validate addresses passed to them. As such, it is possible to overwrite arbitrary memory or execute attacker-supplied code in the context of the kernel (RING 0).
Exploitation allows an attacker to elevate privileges by overwriting arbitrary system memory or executing code within kernel context.
iDefense has confirmed the existence of this vulnerability in our vulnerability lab. The configuration at verification time was as follows:
All products using Trend Micro's scan engine should be considered vulnerable.
Removing write permissions for "Everyone" appears to prevent access to the vulnerable code. iDefense confirmed that the virus scanning engine was still able to detect viruses. Although no side effects were witnessed in Lab tests, normal functionality may be hindered.
"To address this vulnerability, Trend Micro recommends to customers to update their Anti-Rootkit Common Module to version 1.600-1052.
Products that are set to Automatic Update will be updated immediately.
Manual Updating can also be performed by using the product’s “Update Now” function."
More information is available in Trend Micro's knowledge base at the link shown below.
A Mitre Corp. Common Vulnerabilities and Exposures (CVE) number has not been assigned yet.
01/17/2007 Initial vendor notification
01/19/2007 Initial vendor response
02/07/2007 Coordinated public disclosure
This vulnerability was reported to iDefense by Rubén Santamarta of reversemode.com.
Get paid for vulnerability research
Free tools, research and upcoming events
Copyright © 2006 Verisign, Inc.
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 customer service 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.