From owner-freebsd-security Tue Oct 22 04:14:20 1996 Return-Path: owner-security Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA22916 for security-outgoing; Tue, 22 Oct 1996 04:14:20 -0700 (PDT) Received: from smokey.systemics.com (smokey.systemics.com [193.67.124.65]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA22894 for ; Tue, 22 Oct 1996 04:14:14 -0700 (PDT) Received: from kampai.systemics.com (3U88WtZNTe9IQI/9w/r7zPFuXpoBobtj@internal-mail.systemics.com [193.67.124.74]) by smokey.systemics.com (8.6.12/8.6.12) with SMTP id NAA18739; Tue, 22 Oct 1996 13:14:11 +0200 Message-ID: <326CAC94.5358CBEE@systemics.com> Date: Tue, 22 Oct 1996 13:14:28 +0200 From: Gary Howland Organization: Systemics Ltd. X-Mailer: Mozilla 3.0 (X11; I; FreeBSD 2.2-960501-SNAP i386) MIME-Version: 1.0 To: Steve Reid CC: security@freebsd.org Subject: Re: [bugtraq] Serious Linux Security Bug References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-security@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Steve Reid wrote: > > This has been discussed on the Bugtraq list for a few days now, but I > haven't seen any talk of it here. > > There is no mention of the attack working against *BSD machines except for > one person running FreeBSD 2.1.5 who reported that his Intel EtherExpress > card stopped working for a couple of minutes. > > The attack is simple. From a Win95 box, > ping -l 65510 buggyhost > and it can crash or reboot some OSs. Very nasty. > > Has anyone checked the FreeBSD kernel to make sure that we're not > vulnerable? I've tried it on 2.1 and 2.2 and they behave OK (although they don't reply to the ping, unlike a windoze machine). I was trying to emulate the problem with a small perl script, but haven't got a suitable "target". Anyone out there care to test it for me? Best regards, Gary -- pub 1024/C001D00D 1996/01/22 Gary Howland Key fingerprint = 0C FB 60 61 4D 3B 24 7D 1C 89 1D BE 1F EE 09 06