July 10, 2012
Microsoft Visual Basic for Applications is prone to a vulnerability that lets attackers execute arbitrary code. An attacker can exploit this issue by enticing a legitimate user to use the vulnerable application to open a file from a network share location which contains a specially crafted Dynamic Link Library (DLL) file. Successful exploits will compromise the application in the context of the currently logged-in user.
- Microsoft Office 2003 SP3
- Microsoft Office 2010 (32-bit edition)
- Microsoft Office 2010 (32-bit edition) SP1
- Microsoft Office 2010 (64-bit edition)
- Microsoft Office 2010 (64-bit edition) SP1
- Microsoft Visual Basic for Applications
- Microsoft Visual Basic for Applications SDK
Block external access at the network boundary, unless external parties require service.
If global access isn't needed, filter access to the affected computer at the network boundary. Restricting access to only trusted computers and networks might greatly reduce the likelihood of successful exploits.
Run all software as a nonprivileged user with minimal access rights.
To reduce the impact of latent vulnerabilities, always run nonadministrative software as an unprivileged user with minimal access rights.
Do not follow links provided by unknown or untrusted sources.
To reduce the likelihood of successful attacks, never follow links provided by unknown or untrusted individuals.
The vendor has released an advisory and updates. Please see the references for details.
Bai Haowen of Huawei Security Labs
© 1995- Symantec Corporation
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from firstname.lastname@example.org.
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.
Symantec, Symantec products, Symantec Security Response, and email@example.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.