3Com

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Alcatel

Notified:  August 12, 2004 Updated: September 08, 2005

Status

  Vulnerable

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see http://www.niscc.gov.uk/niscc/docs/re-20050412-00303.pdf?lang=en.

Allied Telesyn International

Updated:  April 29, 2005

Status

  Vulnerable

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

For customers in Japan, Allied Telesis K.K. which is a member of AT-Group has published a statement only for Japanese market. Please visit the following web sites. http://jvn.jp/niscc/532967/522154/index.html (Japanese) http://www.allied-telesis.co.jp/support/list/faq/vuls/vulsall.html (Japanese)

Apple Computer, Inc.

Notified:  August 12, 2004 Updated: April 12, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see http://www.niscc.gov.uk/niscc/docs/re-20050412-00303.pdf?lang=en. Apple Mac OS X versions prior to 10.2 may be affected.

AT&T

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Avaya

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Avici Systems Inc.

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Borderware

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Charlotte's Web Networks

Notified:  August 12, 2004 Updated: September 08, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Check Point

Notified:  August 12, 2004 Updated: April 12, 2005

Status

  Not Vulnerable

Vendor Statement

Check Point products are not vulnerable to this issue.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see http://www.niscc.gov.uk/niscc/docs/re-20050412-00303.pdf?lang=en.

Chiaro Networks

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Cisco Systems, Inc.

Notified:  August 12, 2004 Updated: April 12, 2005

Status

  Vulnerable

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see http://www.cisco.com/warp/public/707/cisco-sa-20050412-icmp.shtml.

Clavister

Notified:  August 12, 2004 Updated: April 12, 2005

Status

  Not Vulnerable

Vendor Statement

Clavister Firewall is itself not vulnerable to this class of attacks. It also attempts to protect clients against such attacks. Specifically: No ICMP errors are passed by default. They may however be allowed on a per-rule/service basis. The firewall's own TCP stack (used by internal processes and ALGs) does not listen ICMP errors at all. All sequence numbers are scrambled using a high quality random engine, making sequence number guessing harder. In the case of many-to-one (dynamic) NAT, source port numbers are allocated randomly, making source port number guessing harder. See draft-gont-tcpm-icmp-attacks-00 section 5.3 On not accepting ICMP errors: The method outlined in draft-gont-tcpm-icmp-attacks-00 section 5.2 (delaying the connection reset) results in behavior not too dissimilar. The difference simply lies in how many packets that get sent before the connection is failed. PMTU discovery problems that normally arise by not accepting ICMP errors by default are avoided by doing DF bit stripping by default.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Computer Associates

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Cray Inc.

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Cyber Guard

Updated:  April 12, 2005

Status

  Not Vulnerable

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see http://www.niscc.gov.uk/niscc/docs/re-20050412-00303.pdf?lang=en.

Data Connection

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Debian Linux

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Dlink

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

EMC Corporation

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Engarde

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Enterasys Networks

Updated:  June 15, 2005

Status

  Not Vulnerable

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see

eSoft

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Extreme Networks

Notified:  August 12, 2004 Updated: April 21, 2005

Status

  Vulnerable

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Extreme Networks products running "Extremeware 7.x" software are vulnerable to this issue. Extreme Networks products running "Extremeware EXOS" software are not vulnerable. Workaround: Apply filter to block ICMP packets with specific type/code which can cause the attack.

F5 Networks, Inc.

Notified:  August 12, 2004 Updated: May 03, 2005

Status

  Vulnerable

Vendor Statement

F5 products BIG-IP 4.x and 9.x are vulnerable. Patches are being made ready. TrafficShield and FirePass are not vulnerable.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Further information is available in Secunia Advisory SA15205.

Fedora Project

Notified:  August 12, 2004 Updated: April 12, 2005

Status

  Not Vulnerable

Vendor Statement

CAN-2004-0790: A blind TCP connection reset by sending The Linux 2.4 and 2.6 kernels have always verified the TCP sequence number on ICMP errors. In addition Linux kernels will never abort a connection due to a received ICMP packet. All Fedora Core versions are therefore unaffected by this issue. CAN-2004-0791: A spoofing attack with ICMP type 4 header The Linux kernel since 2.6.9 and 2.4.28 has included a patch by Dave Miller to ignore ICMP Source Quench messages as recommended by Fernando Gont. Fedora Core 3 shipped with a 2.6.9 kernel which ignores ICMP Source Quench messages. Fedora Core 2 was updated to a 2.6.9 kernel in a November 2004 update and is therefore also unaffected by this issue. CAN-2004-1060: ICMP path MTU spoofing Linux 2.4 and 2.6 kernels verify the sequence number on ICMP errors, thus significantly mitigating this issue. This issue can also be mitigated by disabling pmtu discovery if not required (/proc/sys/net/ipv4/ip_no_pmtu_disc)

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see http://www.niscc.gov.uk/niscc/docs/re-20050412-00303.pdf?lang=en.

Fortinet

Notified:  August 12, 2004 Updated: April 21, 2005

Status

  Not Vulnerable

Vendor Statement

Fortinet does not have this problem.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Foundry Networks Inc.

Notified:  August 12, 2004 Updated: April 12, 2005

Status

  Not Vulnerable

Vendor Statement

Foundry's implementation of ICMP on its products is not vulnerable to this type of attack.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

FreeBSD, Inc.

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Fujitsu

Notified:  August 12, 2004 Updated: September 08, 2005

Status

  Not Vulnerable

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see http://www.niscc.gov.uk/niscc/docs/re-20050412-00303.pdf?lang=en, http://software.fujitsu.com/jp/security/niscc/niscc.html#222750-tcpicmp, and http://jvn.jp/niscc/532967/index.html (Japanese).

GTA

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Hewlett-Packard Company

Notified:  August 12, 2004 Updated: September 08, 2005

Status

  Vulnerable

Vendor Statement

SOURCE: Hewlett-Packard CompanySoftware Security Response Team x-ref:SSRT4884 HP is investigating the potential impact to HP's products. As further information becomes available HP will provide notice through standard security bulletin announcements. To report potential security vulnerabilities in HP software, send an E-mail message to security-alert@hp.com.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see HPSBUX01164/SSRT4884 (HP-UX) and HPSBTU01210/SSRT4743 (HP Tru64 UNIX).

Hitachi

Notified:  August 12, 2004 Updated: September 08, 2005

Status

  Vulnerable

Vendor Statement

[[VULNERABLE]
Hitachi GR2000/GR4000/GS4000/GS3000 are vulnerable to this issue. More details are available at (Japanese).] [NOT VULNERABLE] Alaxala AX series are NOT vulnerable.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see http://www.niscc.gov.uk/niscc/docs/re-20050412-00303.pdf?lang=en and http://jvn.jp/niscc/532967/index.html (Japanese).

Hyperchip

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

IBM Corporation

Notified:  August 12, 2004 Updated: April 12, 2005

Status

  Vulnerable

Vendor Statement

The AIX Operating System is affected by the issues discussed in CERT Vulnerability note VU#222750 and NISCC vulnerability #432967. An advisory for this issue will be available via https://techsupport.services.ibm.com/server/pseries.subscriptionSvcs For information related to this and other published CERT Advisories that may relate to the IBM eServer Platforms (xSeries, iSeries, pSeries, and zSeries) please go to https://app-06.www.ibm.com/servers/resourcelink/lib03020.nsf/pages/securityalerts?OpenDocument&pathID= In order to access this information you will require a Resource Link ID. To subscribe to Resource Link go to http://app-06.www.ibm.com/servers/resourcelink and follow the steps for registration. All questions should be refferred to servsec@us.ibm.com.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see http://www.niscc.gov.uk/niscc/docs/re-20050412-00303.pdf?lang=en.

Immunix

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Ingrian Networks, Inc.

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Intel

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Intoto

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Not Vulnerable

Vendor Statement

We analyzed the potential threats discussed in the IETF draft draft-gont-tcpm-icmp-attacks-00.txt and observed that Intoto products are not vulnerable to the described denial of service (DoS) attacks.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

IP Filter

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Juniper Networks, Inc.

Notified:  August 12, 2004 Updated: May 05, 2005

Status

  Vulnerable

Vendor Statement

Juniper Networks M-series and T-series routers running software built prior to August 18, 2004, are susceptible to this vulnerability. Software built on or after that date disables processing of ICMP Source Quench messages, permits the user to disable Path MTU Discovery, and has additional verification enabled for PMTUD. The various forms of ICMP Unreachable messages are already ignored except during session establishment. Other Juniper Networks products are not susceptible to this vulnerability. Customers should visit the Juniper Networks Customer Service Center web-site for further information: http://www.juniper.net/customers/csc

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see http://www.niscc.gov.uk/niscc/docs/re-20050412-00303.pdf?lang=en and https://www.juniper.net/customers/csc.

Lachman

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Linksys

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Lucent Technologies

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Luminous

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Mandriva, Inc.

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Mandriva, Inc.

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Microsoft Corporation

Notified:  August 12, 2004 Updated: April 29, 2005

Status

  Vulnerable

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see Microsoft Security Bulletin MS05-019.

MontaVista Software, Inc.

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Multinet

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Multi-Tech Systems Inc.

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

NEC Corporation

Notified:  August 12, 2004 Updated: September 08, 2005

Status

  Not Vulnerable

Vendor Statement

NEC Corporation products are not susceptible to this vulnerability. We continue to check our products. For more detail: http://www.sw.nec.co.jp/psirt/index.html (Japanese)

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see http://www.niscc.gov.uk/niscc/docs/re-20050412-00303.pdf?lang=en.

NetBSD

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Netfilter

Notified:  August 12, 2004 Updated: April 29, 2005

Status

  Vulnerable

Vendor Statement

The Linux kernel TCP/IP implementation has always been verifying the TCP sequence number embedded into the ICMP packet, and Linux end hosts are thus not affected by this vulnerability. As for non-Linux machines protected by a netfilter/iptables firewall: netfilter/iptables did not implement TCP sequence number (aka window) tracking at all until linux-2.6.9. However, even in linux >= 2.6.9, the check for RELATED ICMP packets does not verify the tcp sequence number of the encapsulated packet. Implementation of such a check is scheduled for inclusion into the 2.6.11 linux kernel.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Netscreen

Notified:  August 12, 2004 Updated: April 12, 2005

Status

  Not Vulnerable

Vendor Statement

Juniper Networks M-series and T-series routers running certain releases of JUNOS software are susceptible to this vulnerability. Other Juniper Networks products are not susceptible to this vulnerability. Customers should visit the Juniper Networks Customer Service Center web-site for further information. http://www.juniper.net/customers/csc

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Network Appliance

Notified:  August 12, 2004 Updated: April 11, 2005

Status

  Vulnerable

Vendor Statement

The Data ONTAP operating system has historically implemented some, but not all, of the recommendations from http://www.ietf.org/internet-drafts/draft-gont-tcpm-icmp-attacks-03.txt NetApp has implemented the remaining recommendations under bug ID 138865. Customers may, as always, check bug status and download patches from http://now.netapp.com/

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Network Associates

Notified:  August 12, 2004 Updated: April 12, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

NextHop

Notified:  August 12, 2004 Updated: April 21, 2005

Status

  Unknown

Vendor Statement

NextHop Technologies software does not include a TCP/IP stack. Instead, it relies on third party TCP/IP stacks. As a result, NextHop software is not directly affected by this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Nokia

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Nortel Networks, Inc.

Notified:  August 12, 2004 Updated: September 08, 2005

Status

  Vulnerable

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see Nortel Technical Bulletins 2005005697, 2005005700, and 2005005701 on the Nortel Securitiy Advisory Bulletins site.

Novell, Inc.

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

OpenBSD

Notified:  August 12, 2004 Updated: April 21, 2005

Status

  Vulnerable

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see 027: RELIABILITY FIX: August 25, 2004 for OpenBSD 3.4 and 015: RELIABILITY FIX: August 25, 2004 for OpenBSD 3.5.

Openwall GNU/*/Linux

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Polycom Inc.

Updated:  September 08, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see http://www.niscc.gov.uk/niscc/docs/re-20050412-00303.pdf?lang=en and the Security Headlines posted at the Polycom Security Center.

Redback Networks Inc.

Notified:  August 12, 2004 Updated: April 12, 2005

Status

  Vulnerable

Vendor Statement

Like most of TCP implementations, both product lines of Redback Networks, Subscriber Management System and SmartEdge Router Family are affected by this vulnerability. The fixes will be available on both platforms in upcoming releases. For further assistance regarding this topic contact the Redback Networks Technical Assistance Center (TAC). TAC is prepared to provide worldwide support for security workarounds that address this issue. The Redback domestic TAC number is (877) 733 2225 and International TAC phone number is 31-104987777. Redback TAC will provide detailed information to our worldwide systems engineers and focal engineers to assist customers in configuring these workarounds.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Red Hat, Inc.

Notified:  August 12, 2004 Updated: April 12, 2005

Status

  Vulnerable

Vendor Statement

CAN-2004-0790: A blind TCP connection reset Red Hat Enterprise Linux 2.1 and 3 kernels have always verified the TCP sequence number on ICMP errors. In addition Linux kernels will never abort a connection due to a received ICMP packet. All Red Hat Enterprise Linux versions are therefore unaffected by this issue. CAN-2004-0791: A spoofing attack with ICMP type 4 header Red Hat Enterprise Linux 2.1 and 3 kernels prior to January 2005 honour ICMP Source Quench messages, although the TCP sequence number is checked which substantially increases the amount of effort an attacker would need to be able to cause a sucessful attack. ICMP Source Quench messages were disabled completely by the following updates: http://rhn.redhat.com/errata/RHSA-2005-043.html http://rhn.redhat.com/errata/RHSA-2005-016.html http://rhn.redhat.com/errata/RHSA-2005-017.html CAN-2004-1060: ICMP path MTU spoofing Red Hat Enterprise Linux 2.1 and 3 kernels verify the sequence number on ICMP errors, thus significantly mitigating this issue. This issue can also be mitigated by disabling pmtu discovery if not required (/proc/sys/net/ipv4/ip_no_pmtu_disc)

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see http://www.niscc.gov.uk/niscc/docs/re-20050412-00303.pdf?lang=en.

Riverstone Networks

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

SCO

Notified:  August 12, 2004 Updated: April 12, 2005

Status

  Vulnerable

Vendor Statement

SCO is aware of the issue and is working on a fix.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

For UnixWare 7.1.4 the fix is included in maintenance pack 2: http://www.sco.com/support/update/download/release.php?rid=58

Secure Computing Corporation

Notified:  August 12, 2004 Updated: April 12, 2005

Status

  Not Vulnerable

Vendor Statement

Secure Computing has carefully analyzed the scenarios outlined in the Internet Draft, and has determined that the Sidewinder G2 responds appropriately in those situations. Some of the scenarios mentioned in this draft illustrate again the desirability of using carefully configured security appliances and using protocols such as IPsec.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see http://www.niscc.gov.uk/niscc/docs/re-20050412-00303.pdf?lang=en.

SecureWorks

Updated:  May 03, 2005

Status

  Not Vulnerable

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

SecureWorx

Notified:  August 12, 2004 Updated: May 03, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Sequent Computer Systems, Inc.

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

SGI

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Sony Corporation

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Stonesoft

Notified:  August 12, 2004 Updated: April 12, 2005

Status

  Not Vulnerable

Vendor Statement

Stonesoft StoneGate Firewall and IPS products are not affected by these vulnerabilities.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see http://www.niscc.gov.uk/niscc/docs/re-20050412-00303.pdf?lang=en.

Sun Microsystems, Inc.

Notified:  August 12, 2004 Updated: April 12, 2005

Status

  Vulnerable

Vendor Statement

Sun is only marginally impacted by the issues described in Gont's ICMP Internet Draft as existing TCP connections will not be dropped. There may be a performance impact but no more or less than flooding any link or system with garbage messages will cause performance problems. Sun is issuing Sun Alert 57746 to further describe Sun's specific impact and details which will be available here: http://sunsolve.sun.com/search/document.do?assetkey=1-26-57746-1

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

SUSE Linux

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Symantec Corporation

Notified:  August 12, 2004 Updated: May 03, 2005

Status

  Vulnerable

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see SYM05-008.

Tech Matrix

Updated:  April 29, 2005

Status

  Not Vulnerable

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see http://jvn.jp/niscc/532967/index.html (Japanese).

TurboLinux

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Unisys

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

WatchGuard

Notified:  August 12, 2004 Updated: April 11, 2005

Status

  Vulnerable

Vendor Statement

All WatchGuard firewalls are impacted to some extent by Gont's findings. TCP sessions which terminate on or pass through the firewall are vulnerable to reset attacks when the attacker can guess the source and destination address and port combinations for that session. WatchGuard plans to address the issues raised by Gont's paper for all products in software releases currently scheduled for the Q2-Q3 2005 time frame. If you have further questions about this or any other security concern with WatchGuard products, please contact: Steve Fallin Director, Rapid Response Team WatchGuard Technologies http://www.watchguard.com steve.fallin@watchguard.com +1.206.521.8340

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.

Wind River Systems, Inc.

Notified:  August 12, 2004 Updated: April 12, 2005

Status

  Vulnerable

Vendor Statement

In all releases after VxWorks 5.3 a hard error does not result in TCP aborting the connection. The hard error code is saved by TCP. If the connection is dropped due to a timeout this error code is available to the application. Wind River Network Stack 2.0 already checks the ICMP sequence numbers. The release of VxWorks 6.0 and the MSP updates shipping in the fall of 2004 are based on this stack. Wind River is planning updates to the VxWorks 5.5 and 5.4 versions of the stack that will include the fix for ICMP. These updates are planned for 2005.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see http://www.niscc.gov.uk/niscc/docs/re-20050412-00303.pdf?lang=en.

Yamaha

Updated:  April 29, 2005

Status

  Not Vulnerable

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

Please see http://jvn.jp/niscc/532967/index.html (Japanese).

ZyXEL

Notified:  August 12, 2004 Updated: February 07, 2005

Status

  Unknown

Vendor Statement

No statement is currently available from the vendor regarding this vulnerability.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

US-CERT has no additional comments at this time.