Date Discovered April 13, 2010
Description Microsoft Publisher is prone to a remote buffer-overflow vulnerability.
An attacker can exploit this issue by enticing a victim to open a malicious Publisher file.
Successfully exploiting this issue would allow an attacker to execute arbitrary code in the context of the currently logged-in user.
- Microsoft Publisher 2002
- Microsoft Publisher 2002 SP3
- Microsoft Publisher 2003
- Microsoft Publisher 2003 SP2
- Microsoft Publisher 2003 SP3
- Microsoft Publisher 2007
- Microsoft Publisher 2007 SP1
- Microsoft Publisher 2007 SP2
Run all software as a nonprivileged user with minimal access rights. To mitigate the impact of a successful exploit, run the affected application as a user with minimal access rights.
Deploy network intrusion detection systems to monitor network traffic for malicious activity. Deploy NIDS to monitor network traffic for signs of suspicious or anomalous activity. This may help detect malicious actions that an attacker may take after successfully exploiting vulnerabilities in applications. Review all applicable logs regularly.
Do not accept or execute files from untrusted or unknown sources. Never accept files from untrusted or unknown sources, because they may be malicious in nature. Avoid opening email attachments from unknown or questionable sources.
Implement multiple redundant layers of security.
Since this issue may be leveraged to execute code, we recommend memory-protection schemes, such as nonexecutable stack/heap configurations and randomly mapped memory segments. This tactic may complicate exploit attempts of memory-corruption vulnerabilities.
The vendor has released an advisory and updates. Please see the references for details.
Credits Lionel d'Hauenen working with TippingPoint’s Zero Day Initiative
Copyright © 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.