Vulnerability Note VU#476900

Microsoft Outlook fails to properly process a VEVENT record

Overview

Microsoft Outlook contains a memory corruption vulnerability that could enable an attacker to execute arbitrary code and gain complete control of the vulnerable system.

I. Description

Microsoft Outlook fails to properly handle malformed VEVENT records. When an .iCal meeting request containing a VEVENT record is opened, Outlook does not properly perform data validation on the record. An attacker could send a specially crafted .ics file in the request that, when opened, could corrupt system memory allowing the attacker to execute arbitrary code. The attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.

II. Impact

An attacker could gain complete control of the affected system and execute arbitrary code.

III. Solution

Microsoft addresses this vulnerability with the updates listed in Microsoft Security Bulletin MS07-003. Note that Microsoft has documented known issues that occur after applying this update. See Microsoft Knowledgebase article 925938 for details.

Users whose accounts are configured to have fewer user rights on the system could be less affected than users who operate with administrative user rights.

Systems Affected

Vendor	Status	Date Updated
Microsoft Corporation	Vulnerable	9-Jan-2007

References

http://www.microsoft.com/technet/security/Bulletin/MS07-003.mspx
http://support.microsoft.com/kb/925542/
http://support.microsoft.com/kb/931270/
http://support.microsoft.com/kb/925938
http://securitytracker.com/alerts/2007/Jan/1017488.html
http://secunia.com/advisories/23674/
http://www.securityfocus.com/bid/21931

Credit

Thanks to Lurene Grenier of Sourcefire for reporting this vulnerability.

This document was written by Joseph W Pruszynski.

Other Information

Date Public	01/09/2007
Date First Published	01/09/2007 02:45:15 PM
Date Last Updated	01/26/2007
CERT Advisory
CVE Name	CVE-2007-0033
Metric	60.24
Document Revision	23

If you have feedback, comments, or additional information about this vulnerability, please send us email.