November 16, 2007
Microsoft Jet Database Engine is prone to a buffer-overflow vulnerability because it fails to properly bounds-check user-supplied data. Remote attackers can exploit this issue to execute arbitrary machine code in the context of a user running the application. Successful exploits will compromise the affected application and possibly the underlying computer. Failed attacks will likely cause denial-of-service conditions. NOTE: Further details report that attackers are using malicious Word files to load specially crafted MDB files. Microsoft has released a knowledge base article (950627) documenting this attack vector. This issue does not affect Windows Server 2003 Service Pack 2, Windows XP Service Pack 3, Windows XP x64 edition Server Pack 2, Windows Vista, Windows Vista Service Pack 1 and Windows Server 2008 because they run a version of the Jet Database Engine that isn’t vulnerable. This issue does affect the Jet Database Engine, Microsoft Word 2000 Service Pack 3, Microsoft Word 2002 Service Pack 3, Microsoft Word 2003 Service Pack 2, Microsoft Word 2003 Service Pack 3, Microsoft Word 2007, and Microsoft Word 2007 Service Pack 1 on Microsoft Windows 2000, Windows XP, or Windows Server 2003 Service Pack 1.
- Avaya Messaging Application Server
- Avaya Messaging Application Server MM 1.1
- Avaya Messaging Application Server MM 2.0
- Avaya Messaging Application Server MM 3.0
- Avaya Messaging Application Server MM 3.1
- HP Storage Management Appliance 2.1
- HP Storage Management Appliance I
- HP Storage Management Appliance II
- HP Storage Management Appliance III
- Microsoft Access 2000
- Microsoft Access 2000 SP2
- Microsoft Access 2000 SP3
- Microsoft Access 2000 SR1
- Microsoft Access 2002
- Microsoft Access 2002 SP1
- Microsoft Access 2002 SP2
- Microsoft Access 2003
- Microsoft JET 2.0
- Microsoft JET 2.5
- Microsoft JET 3.0
- Microsoft JET 3.5
- Microsoft JET 3.51
- Microsoft JET 3.51 SP3
- Microsoft JET 4.0
- Microsoft JET 4.0 SP1
- Microsoft JET 4.0 SP2
- Microsoft JET 4.0 SP3
- Microsoft JET 4.0 SP4
- Microsoft JET 4.0 SP5
- Microsoft JET 4.0 SP6
- Microsoft JET 4.0 SP7
- Microsoft Word 2000 SP3
- Microsoft Word 2002 SP3
- Microsoft Word 2003 SP2
- Microsoft Word 2003 SP3
- Microsoft Word 2007
- Microsoft Word 2007 SP1
- Nortel Networks Centrex IP Client Manager 10.0
- Nortel Networks Centrex IP Client Manager 9.0
- Nortel Networks Media Processing Svr 100
- Nortel Networks Media Processing Svr 1000 Rel 3.0
- Nortel Networks Media Processing Svr 500 Rel 3.0
- Nortel Networks Self Service VoiceXML
- Nortel Networks Self-Service – CCSS7
- Nortel Networks Self-Service CCXML
- Nortel Networks Self-Service Peri Application
- Nortel Networks Self-Service Peri Workstation
- Nortel Networks Self-Service Speech Server
- Nortel Networks Self-Service WVADS
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of anomalous or suspicious activity. This includes but is not limited to requests that include NOP sleds and unexplained incoming and outgoing traffic. This may indicate exploit attempts or activity that results from a successful exploit.
Run all software as a nonprivileged user with minimal access rights.
To reduce the impact of a successful exploit, run all applications with the least amount of privileges possible.
Do not accept or execute files from untrusted or unknown sources.
To reduce the likelihood of successful exploits, never handle files that originate from unfamiliar or untrusted sources.
Do not follow links provided by unknown or untrusted sources.
Web users should be cautious about following links to sites that are provided by unfamiliar or suspicious sources.
Filtering HTML from emails may help remove a possible vector for transmitting malicious links to users.
Implement multiple redundant layers of security.
Various memory-protection schemes (such as nonexecutable and randomly mapped memory segments) may hinder an attacker’s ability to exploit this vulnerability to execute arbitrary code.
The vendor released updates to address this issue. Please see the references for more information.
cocoruder is credited with the discovery of this issue.
© 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 email@example.com.
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 firstname.lastname@example.org 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.