From owner-freebsd-security Mon Oct 21 14:58:35 1996 Return-Path: owner-security Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA16198 for security-outgoing; Mon, 21 Oct 1996 14:58:35 -0700 (PDT) Received: from glacier.cold.org (glacier.cold.org [206.81.134.54]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id OAA16188 for ; Mon, 21 Oct 1996 14:58:26 -0700 (PDT) Received: from localhost (brandon@localhost) by glacier.cold.org (8.7.5/8.7.3) with SMTP id QAA00169; Mon, 21 Oct 1996 16:00:20 -0600 (MDT) Date: Mon, 21 Oct 1996 16:00:20 -0600 (MDT) From: Brandon Gillespie To: Steve Reid cc: security@freebsd.org Subject: Re: [bugtraq] Serious Linux Security Bug In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-security@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 21 Oct 1996, 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 just tried this (from w95) against a FreeBSD 2.1.5 box and a 2.1.0 box, both had no problems. Of course, I'm not sure if the ping ran correctly, it returned: Request timed out. Instead. It does work without the '-l 65510' args. -Brandon