From owner-freebsd-i386@FreeBSD.ORG Thu May 6 05:05:46 2004 Return-Path: Delivered-To: freebsd-i386@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D552916A4CE; Thu, 6 May 2004 05:05:46 -0700 (PDT) Received: from gw.celabo.org (gw.celabo.org [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B70E43D53; Thu, 6 May 2004 05:05:46 -0700 (PDT) (envelope-from nectar@celabo.org) Received: by gw.celabo.org (Postfix, from userid 1001) id 333B25485D; Thu, 6 May 2004 07:05:46 -0500 (CDT) Date: Thu, 6 May 2004 07:05:46 -0500 From: "Jacques A. Vidrine" To: "Simon L. Nielsen" Message-ID: <20040506120546.GA48593@hellblazer.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , "Simon L. Nielsen" , freebsd-i386@FreeBSD.org, security@FreeBSD.org References: <200405060932.i469W3eB087890@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200405060932.i469W3eB087890@freefall.freebsd.org> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.4i cc: freebsd-i386@FreeBSD.org cc: security@FreeBSD.org Subject: Re: i386/66311: TCPDUMP ISAKMP payload handling denial-of-service Vulnerability X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 May 2004 12:05:47 -0000 On Thu, May 06, 2004 at 02:32:03AM -0700, Simon L. Nielsen wrote: > Synopsis: TCPDUMP ISAKMP payload handling denial-of-service Vulnerability > > Responsible-Changed-From-To: freebsd-i386->security > Responsible-Changed-By: simon > Responsible-Changed-When: Thu May 6 02:30:15 PDT 2004 > Responsible-Changed-Why: > Reassign to the Security Team for evaluation of the severity of this > problem. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=66311 [This PR seems to be misfiled as `i386' ?] This is the issue documented here: http://vuxml.freebsd.org/f8551668-de09-4d7b-9720-f1360929df07.html It is already repaired in -CURRENT. The security team does not have any special action planned due to the extremely limited impact of the issue. The tcpdump maintainer (fenner@) should probably be contacted about an MFC. Cheers, -- Jacques Vidrine / nectar@celabo.org / jvidrine@verio.net / nectar@freebsd.org