Original release date: May 10, 2002<br> Last revised: August 28, 2002<br> Source: CERT/CC<br> <p> A complete revision history can be found at the end of this file. </p> <a name="affected"></a> <h3> Systems Affected </h3> <p> Microsoft Windows systems with one or more of the following: <ul> <li>Microsoft MSN Chat control</li> <li>Microsoft MSN Messenger 4.6 and prior</li> <li>Microsoft Exchange Instant Messenger 4.6 and prior</li> </ul> </p> <a name="overview"></a> <h2> Overview </h2> <p> Microsoft's MSN Chat is an ActiveX control for Microsoft Messenger, an instant messaging client. A buffer overflow exists in the ActiveX control that may permit a remote attacker to execute arbitrary code on the system with the privileges of the current user. </p> <a name="description"></a> <h2> I. Description </h2> <p> A buffer overflow exists in the "ResDLL" parameter of the MSN Chat ActiveX control that may permit a remote attacker to execute arbitrary code on the system with the privileges of the current user. This vulnerability affects MSN Messenger and Exchange Instant Messenger users. Since the control is signed by Microsoft, users of Microsoft's Internet Explorer (IE) who accept and install Microsoft-signed ActiveX controls are also affected. The Microsoft MSN Chat control is also available for direct download from the web. </p> <p> The <object> tag could be used to embed the ActiveX control in a web page. If an attacker can trick the user into visiting a malicious site or the attacker sends the victim a web page as an HTML-formatted email message or newsgroup posting then this vulnerability could be exploited. This acceptance and installation of the control can occur automatically within IE for users who trust Microsoft-signed ActiveX controls. When the web page is rendered, either by opening the page or viewing the page through a preview pane, the ActiveX control could be invoked. Likewise, if the ActiveX control is embedded in a Microsoft Office (Word, Excel, etc.) document, it may be executed when the document is opened. </p> <p> According to the <a href="http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/bulletin/MS02-022.asp">Microsoft Advisory (MS02-022)</a>:</p> <blockquote> It's important to note that this control is used for chat rooms on several MSN sites in addition to the main MSN Chat site. If you have successfully used chat on any MSN-site, you have downloaded and installed the chat control. </blockquote> <p> The CERT/CC has published information on ActiveX in <a href="http://www.cert.org/reports/activeX_report.pdf"><i>Results of the Security in ActiveX Workshop</i> (pdf)</a> and <a href="http://www.cert.org/advisories/CA-2000-07.html">CA-2000-07</a>. </p> <p> This issue is also being referenced as <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2002-0155">CAN-2002-0155</a>: </p> <blockquote> <a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2002-0155">http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2002-0155</a> </blockquote> <a name="impact"></a> <h2> II. Impact </h2> <p> A remote attacker may be able to execute arbitrary code with the privileges of the current user. </p> <a name="solution"></a> <h2> III. Solution </h2> <p> <b>Apply a patch from your vendor</b> </p> <b><p>On June 11, 2002, Microsoft updated Microsoft Advisory (MS02-022) and released a new patch that remedies the vulnerability for users that downloaded and accepted the control. The previous solution did not fully protect against this action and it was possible for an attacker to load the vulnerable control, even though the previous patch and updated versions had been installed.</p> <p>The new patch is available at <a href="http://www.microsoft.com/Downloads/Release.asp?ReleaseID=39632">http://www.microsoft.com/Downloads/Release.asp?ReleaseID=39632</a>. All users should apply this patch, even if you previously installed an updated version of your software. This patch supercedes the patch information below.</p></b> <blockquote> <i><p>Microsoft has released a <a href="http://www.microsoft.com/Downloads/Release.asp?ReleaseID=38790">patch</a>, a fixed MSN Chat control, and upgrades to address this issue. It is important that all users apply the <a href="http://www.microsoft.com/Downloads/Release.asp?ReleaseID=38790">patch</a> since it will prevent the installation of the vulnerable control on systems that have not already installed it.</p> <p> Download location for the patch: </p> <blockquote> <a href="http://www.microsoft.com/Downloads/Release.asp?ReleaseID=38790">http://www.microsoft.com/Downloads/Release.asp?ReleaseID=38790</a> </blockquote></i> </blockquote> <p>If you have updated your software prior to June 11, 2002, you should reinstall the software from the following locations:</p> <blockquote> <p> Download location for updated version of MSN Messenger with the corrected control: </p> <blockquote> <a href="http://messenger.msn.com/download/download.asp?client=1&update=1"> http://messenger.msn.com/download/download.asp?client=1&update=1</a> </blockquote> <p> Download location for updated version of Exchange Instant Messenger with the corrected control: </p> <blockquote> <a href="http://www.microsoft.com/Exchange/downloads/2000/IMclient.asp"> http://www.microsoft.com/Exchange/downloads/2000/IMclient.asp</a> </blockquote> </blockquote> <p> Microsoft also suggests that the following Microsoft mail products: Outlook 98 and Outlook 2000 with the <a href="http://office.microsoft.com/Downloads/2000/Out2ksec.aspx">Outlook Email Security Update</a>, Outlook 2002, and Outlook Express will block the exploitation of this vulnerability via email because these products will open HTML email in the Restricted Sites zone. </p> <p> Other mitigation strategies include opening web pages and email messages in the Restricted Sites zone and using email clients that permit users to view messages in plain-text. Likewise, it is important for users to realize that a signed control only authenticates the origin of the control and does not imply any information with regard to the security of the control. Therefore, downloading and installing signed controls through an automated process is not a secure choice. </p> <a name="vendors"></a> <h2> Appendix A. - Vendor Information </h2> <p> This appendix contains information provided by vendors for this advisory. As vendors report new information to the CERT/CC, we will update this section and note the changes in our revision history. If a particular vendor is not listed below, please check the <a href="http://www.kb.cert.org/vuls/id/713779">Vulnerability Note (VU#713779)</a> or contact your vendor directly. </p> <!-- start vendor --> <a name="Microsoft"></a> <h4> <a href="http://www.microsoft.com">Microsoft</a> </h4> <blockquote> See <a href="http://www.microsoft.com/technet/treeview/default.asp?url=/technet/security/bulletin/MS02-022.asp">http://www.microsoft.com/technet/treeview/default.asp ?url=/technet/security/bulletin/MS02-022.asp</a> </blockquote> <!-- end vendor --> <hr> <p> The CERT/CC acknowledges the eEye Team for discovering and reporting on this vulnerability and thanks Microsoft for their technical assistance. </p> <hr noshade> <p>Feedback can be directed to the author: <A HREF="mailto:cert@cert.org?subject=CA-2002-13%20Feedback%20VU%23713779">Jason A. Rafail</p> <p></p> <!--#include virtual="/include/footer_nocopyright.html" --> <p> Copyright 2002 Carnegie Mellon University. </p> <p> Revision History <pre> May 10, 2002: Initial release August 28, 2002: Updated patch information </pre> </p> |