From owner-freebsd-security@FreeBSD.ORG Sat Mar 31 05:41:08 2007 Return-Path: X-Original-To: freebsd-security@freebsd.org Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7D88016A401 for ; Sat, 31 Mar 2007 05:41:08 +0000 (UTC) (envelope-from simon@zaphod.nitro.dk) Received: from mx.nitro.dk (zarniwoop.nitro.dk [83.92.207.38]) by mx1.freebsd.org (Postfix) with ESMTP id 22ACA13C448 for ; Sat, 31 Mar 2007 05:41:07 +0000 (UTC) (envelope-from simon@zaphod.nitro.dk) Received: from zaphod.nitro.dk (unknown [192.168.3.39]) by mx.nitro.dk (Postfix) with ESMTP id 6A1AA2D48A0; Sat, 31 Mar 2007 05:41:05 +0000 (UTC) Received: by zaphod.nitro.dk (Postfix, from userid 3000) id 1778511434; Sat, 31 Mar 2007 07:41:04 +0200 (CEST) Date: Sat, 31 Mar 2007 07:41:04 +0200 From: "Simon L. Nielsen" To: Thomas Vogt Message-ID: <20070331054103.GA982@zaphod.nitro.dk> References: <1175178178.80069.31.camel@bert.mlan.solnet.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1175178178.80069.31.camel@bert.mlan.solnet.ch> User-Agent: Mutt/1.5.11 Cc: freebsd-security@freebsd.org Subject: Re: Integer underflow in the "file" program before 4.20 X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Mar 2007 05:41:08 -0000 On 2007.03.29 16:22:58 +0200, Thomas Vogt wrote: > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-1536 > "Integer underflow in the file_printf function in the "file" program > before 4.20 allows user-assisted attackers to execute arbitrary code via > a file that triggers a heap-based buffer overflow." > > Is FreeBSD 5.x/6.x affected too? It looks the System has file 4.12. The > port has 4.20. Hey, While I haven't confirmed FreeBSD is vulnerable, I assume that is the case. In any case, we (The FreeBSD Security Team) are working on this isuse. -- Simon L. Nielsen FreeBSD Security Team