August 12, 2008
Microsoft Windows is prone to a vulnerability in the IPsec implementation. The vulnerability causes IPsec policies that are imported from a Windows Server 2003 domain to a Windows Server 2008 domain to be ignored. This will cause network traffic to be transmitted in clear text instead of being encrypted.
- Microsoft Windows Server 2008 for 32-bit Systems
- Microsoft Windows Server 2008 for Itanium-based Systems
- Microsoft Windows Server 2008 for x64-based Systems
- Microsoft Windows Vista
- Microsoft Windows Vista Business
- Microsoft Windows Vista Business SP1
- Microsoft Windows Vista Enterprise
- Microsoft Windows Vista Enterprise SP1
- Microsoft Windows Vista Home Basic
- Microsoft Windows Vista Home Basic SP1
- Microsoft Windows Vista Home Premium
- Microsoft Windows Vista Home Premium SP1
- Microsoft Windows Vista SP1
- Microsoft Windows Vista Ultimate
- Microsoft Windows Vista Ultimate SP1
- Microsoft Windows Vista x64 Edition
- Microsoft Windows Vista x64 Edition SP1
Implementing Ethernet switches and binding MAC addresses to switch ports may prevent attacks.
Use network switches to segment the internal network. This may help minimize sniffing to the local network segment.
Communicate sensitive information over encrypted channels.
Use application- or protocol-specific encryption in addition to IPsec when transmitting sensitive information.
Microsoft has released a security bulletin to address this vulnerability.
© 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.