WelcomeEnterpriseSmall BusinessHome & Home OfficePartnersAbout Symantec
16 May, 2002
Symantec Norton Personal Firewall 2002 SYN/FIN scan issue

Risk
Low

Overview
Symantec is aware of two issues with the Symantec Norton Personal Firewall 2002. A Microsoft Windows 2000 system is exposed during a SYN/FIN scan with Symantec Norton Personal Firewall 2002 installed. Additionally, a Jolt2 IP fragmentation attack will succeed against a non-patched Microsoft Windows 2000 computer running Symantec Norton Personal Firewall 2002.

Components Affected
Norton Personal Firewall 2002
Norton Internet Security 2002

Description
On 16 April, 2002, Symantec became aware of a SYN/FIN scan issue reported on SecurityFocus. By using a SYN/FIN scan, an attacker would be able to port scan a Microsoft Windows 2000 computer so that the computer responds even if Symantec Norton Personal Firewall 2002 is installed. A second reported issue states that a plain install of a Microsoft Windows 2000 system with Symantec Norton Personal Firewall 2002 installed is susceptible to a packet fragmentation denial of service (DoS) attack known as Jolt2.

Symantec Response
Symantec has evaluated both issues. Although a Microsoft Windows 2000 computer can be detected through the SYN/FIN scan, Symantec Norton Personal Firewall 2002 continues to protect the computer from an actual intrusion by blocking connections to the computer.

Because Symantec takes the security of its customers very seriously, an update to Symantec Norton Personal Firewall 2002 and Symantec Norton Internet Security 2002 has been made available via Symantec's LiveUpdate to address this concern. Users of Symantec Norton Personal Firewalls running the latest updates are fully protected.

To protect users from Jolt2 DoS attacks against Microsoft Windows 2000 computers, Symantec recommends that Microsoft Windows 2000 Service Pack 1 (SP1) or later be installed. Microsoft Windows 2000 with SP1 or later is not susceptible to this problem. The latest updates for Microsoft products can be obtained from the Microsoft Windows Update site.

As a best practice, Symantec recommends keeping all operating systems and applications updated with the latest vendor patches. Keeping mission-critical systems updated with all security patches applied reduces risk exposure.

Symantec further recommends using a multi-layered approach to security. Users, at a minimum, should run both personal firewall and antivirus applications to provide multiple points of detection and protection to both inbound and outbound threats.


Symantec takes the security and proper functionality of our products very seriously. As founding members of the Organization for Internet Safety (OISafety), Symantec supports and follows the principles of responsible disclosure. Symantec also subscribes to the vulnerability disclosure guidelines outlined by the National Infrastructure Advisory Council (NIAC).

Please contact secure@symantec.com if you feel you have discovered a security issue in a Symantec product. A Symantec Product Security team member will contact you regarding your submission. Symantec strongly recommends using encrypted email for reporting vulnerability information to secure@symantec.com. The Symantec Product Security PGP key can be found at the end of this message.

Symantec has developed a Product Vulnerability Response document outlining the process we follow in addressing suspected vulnerabilities in our products. This document is available below.

Symantec-Product-Vulnerability-Response Symantec Vulnerability Response Policy Symantec Product Vulnerability Management PGP Key Symantec Product Vulnerability Management PGP Key


Copyright (c) 2009 by Symantec Corp.
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 secure@symantec.com.

Disclaimer
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 secure@symantec.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.


Last modified on: Monday, 25-Oct-04 21:53:25