This website uses cookies to distinguish you from other users of our website. The use of cookies helps us to provide you with a specific service, to facilitate website use, to understand our visitors and to advertise to you. By continuing to browse the site you are giving consent to our use of cookies. Learn more in our <a href="/en_IN/privacy/index.xhtml">Privacy Statement</a>.

Security Services

IBM Lotus Notes Office Document Attachment Viewer Stack Buffer Overflow



IBM Corp.'s Lotus Notes software is an integrated desktop client option for accessing e-mail, calendars and applications on an IBM Corp. Lotus Domino server. More information can be found by visiting the URL below.


Remote exploitation of a stack buffer overflow vulnerability in IBM Corp.'s Lotus Notes could allow an attacker to execute arbitrary code in the context of the current user.

The vulnerability occurs during the processing of hyperlink information contained within a Microsoft Office Document (DOC) file. The hyperlink may be crafted in a manner which can cause a strcpy function call to overflow the bounds of a stack buffer. This condition may lead to arbitrary code execution.


Exploitation of this vulnerability results in the execution of arbitrary code in the context of the user opening an attachment delivered via email. In order to be successful, an attacker must social engineer the victim into processing a specially crafted email attachment in a certain way. Specifically, the victim must open the attachment and click the view button on the attachment dialog box.


Lotus Notes versions 6.0, 6.5, 7.0, 8.0, 8.5 are vulnerable.


A workaround is available to disable MS Office Documents within the Lotus Notes file viewer:

Open the keyview.ini file in the Lotus Notes program data directory (C:Program FilesIBMLotusNotesData) and comment out all references to mw8sr.dll. To comment out a reference, proceed the line with a semi-colon ';'.


IBM has released patches and workarounds to address this vulnerability. For more information, consult their advisory at the following URL.


A Mitre Corp. Common Vulnerabilities and Exposures (CVE) number has not been assigned yet.


07/27/2010 Initial Vendor Notification
07/27/2010 Initial Vendor Reply
05/24/2011 Coordinated Public Disclosure


This vulnerability was reported to iDefense by

Get paid for vulnerability research

Free tools, research and upcoming events


Copyright © 2011 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.