Microsoft MSN Messenger video conversations buffer overflow
| msnmessenger-video-bo (36314) |  High Risk |
Description:
Microsoft MSN Messenger is vulnerable to a heap-based buffer overflow, caused by the improper handling of video conversations. By persuading the victim to accept an incoming Web cam invitation and sending specially-crafted data, a remote attacker could overflow a buffer and execute arbitrary code on the system.
*CVSS:
| Base Score: | 7.6 |
| Access Vector: | Network |
| Access Complexity: | High |
| Authentication: | None |
| Confidentiality Impact: | Complete |
| Integrity Impact: | Complete |
| Availability Impact: | Complete |
| Temporal Score: | 6.3 |
| Exploitability: | Functional |
| Remediation Level: | Official-Fix |
| Report Confidence: | Confirmed |
Consequences:
Gain Access
Remedy:
Apply the appropriate patch for your system, as listed in Microsoft Security Bulletin MS07-054. See References.
For Hewlett-Packard:
Refer to HPSBST02260 SSRT071471 for patch, upgrade, or suggested workaround information. See References.
For other distributions:
Contact your vendor for upgrade or patch information.
References:
- HPSBST02260 SSRT071471 : Storage Management Appliance (SMA), Microsoft Patch Applicability MS07-051 to MS07-054.
- Microsoft Corporation Web site: Microsoft MSN Messenger.
- Microsoft Security Bulletin MS07-054: Vulnerability in MSN Messenger and Windows Live Messenger could allow Remote Code Execution (942099).
- Team 509 Web site : MSN VIDEO webcam video conversation, WebCam.
- ASA-2007-376: MS07-054 Vulnerability in MSN Messenger and Windows Live Messenger could allow Remote Code Execution (942099)
- BID-25461: Microsoft MSN Messenger Video Conversation Buffer Overflow Vulnerability
- CVE-2007-2931: Heap-based buffer overflow in Microsoft MSN Messenger 6.2, 7.0, and 7.5, and Live Messenger 8.0 allows user-assisted remote attackers to execute arbitrary code via unspecified vectors involving video conversation handling in Web Cam and video chat sessions.
- SA26570: MSN Messenger Video Conversation Buffer Overflow Vulnerability
- SECTRACK ID: 1018622: MSN Messenger Buffer Overflow in Processing Webcam Streams Lets Remote Users Execute Arbitrary Code
- US-CERT VU#166521: MSN Messenger and Windows Live Messenger webcam stream heap overflow
- VUPEN/ADV-2007-2987: Microsoft MSN Messenger Video Conversation Handling Code Execution (MS07-054)
Platforms Affected:
- HP Storage Management Appliance 2.1
- Microsoft MSN Messenger 6.2
- Microsoft MSN Messenger 7.0
- Microsoft MSN Messenger 7.5
- Microsoft Windows 2000 SP4
- Microsoft Windows 2003 Server SP1
- Microsoft Windows 2003 Server x64
- Microsoft Windows Live Messenger 8.0
- Microsoft Windows Server 2003 SP2
- Microsoft Windows Server 2003 SP2 x64
- Microsoft Windows Vista x64
- Microsoft Windows Vista
- Microsoft Windows XP SP2
- Microsoft Windows XP x64 Professional
- Microsoft Windows XP SP2 x64 Professional
Reported:
Aug 28, 2007
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net
* According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall IBM be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.