Research > Zero-Day Tracker > 20070131
MSN Messenger Video Conversation Heap Overflow
MSN Messenger 6.x
MSN Messenger 7.x
MSN Messenger 8.0.x (not confirmed yet)
A zero-day vulnerability has been publicly documented. This vulnerability lies in the MSN Messenger Webcam component. If an attacker is able to convince a victim to accept an incoming Webcam request, the attacker is then able to run code upon that remote victims host. However, do to the nature of this vulnerability, an attacker is only able to leverage it against victims that accept the webcam request.
Arbitrary code execution under the context of the logged in user
Although this vulnerability has a high impact, because of the level of interaction needed by a victim to accept a webcam invite, the impact will be somewhat limited. A more critical scenario is generated when clients are running with administrator-level privileges on their local hosts, which would run the malicious payload with Administrator credentials.
At this moment, the best form of mitigation is to upgrade MSN Messengers to MSN Messenger Live (version 8.1 or later).
Administrators can block Webcam connections by disabling TCP/1863 at the firewall, which will disable all MSN Video support.
eEye's Blink® Personal Edition protects from this vulnerability.
eEye's Blink® Professional Edition protects from this vulnerability.
eEye's Retina® Network Security Scanner scans devices to detect for this vulnerability.
Windows Live Messenger 8.1
Original Vulnerability Disclosure
1/31/2007: Vulnerability / Reproduction Details Released
9/11/2007: MS07-054 Released From Microsoft
Copyright ©1998-2011 eEye Digital Security
Permission is hereby granted for the redistribution of this alert electronically. It is not to be edited in any way without express consent of eEye. If you wish to reprint the whole or any part of this alert in any other medium excluding electronic medium, please email alert@eEye.com for permission.
The information within this paper may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are no warranties, implied or express, with regard to this information. In no event shall the author be liable for any direct or indirect damages whatsoever arising out of or in connection with the use or spread of this information. Any use of this information is at the user's own risk.