Microsoft Office ASLR Remote Security Bypass Weakness



Date Discovered

May 13, 2014


Microsoft Office is prone to a remote security-bypass weakness that may cause a library to use a predictable base address. This weakness may allow attackers to predict the base address of a library in certain circumstances and in turn bypass the Address Space Layout Randomization (ASLR) protection mechanisms of applications. This may aid in further attacks and lead to arbitrary code execution.

Technologies Affected

  • Microsoft Office 2007 SP3
  • Microsoft Office 2010 (32-bit edition) SP1
  • Microsoft Office 2010 (32-bit edition) SP2
  • Microsoft Office 2010 (64-bit edition) SP1
  • Microsoft Office 2010 (64-bit edition) SP2
  • Microsoft Office 2013 (32-bit editions)
  • Microsoft Office 2013 (64-bit editions)
  • Microsoft Office 2013 RT
  • Microsoft Office 2013 RT Service Pack 1
  • Microsoft Office 2013 Service Pack 1 (32-bit editions)
  • Microsoft Office 2013 Service Pack 1 (64-bit editions)


Block external access at the network boundary, unless external parties require service.
If possible, block access to the server at the network perimeter. Allow only trusted computers and networks to have access to the resources.

Run all software as a nonprivileged user with minimal access rights.
To reduce the impact of a successful exploit, run the hosting webserver in a chrooted or jailed environment with the minimal amount of privileges required for functionality.

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor the network for suspicious requests. This may help detect attacks that try to exploit this and similar vulnerabilities. Audit all applicable logs regularly.

Updates are available. Please see the references or vendor advisory for more information.




© 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


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 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.