From owner-freebsd-security@FreeBSD.ORG Fri Feb 13 08:37:33 2004 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1722516A4CE for ; Fri, 13 Feb 2004 08:37:33 -0800 (PST) Received: from gw.celabo.org (gw.celabo.org [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id E1DD743D1D for ; Fri, 13 Feb 2004 08:37:32 -0800 (PST) (envelope-from nectar@celabo.org) Received: by gw.celabo.org (Postfix, from userid 1001) id 7D8B4548A4; Fri, 13 Feb 2004 10:37:32 -0600 (CST) Date: Fri, 13 Feb 2004 10:37:32 -0600 From: "Jacques A. Vidrine" To: "Barnes, John" Message-ID: <20040213163732.GA73212@hellblazer.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , "Barnes, John" , "'freebsd-security@freebsd.org'" References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.4i cc: "'freebsd-security@freebsd.org'" Subject: Re: XFree86 Font Information File Buffer Overflow X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Feb 2004 16:37:33 -0000 On Fri, Feb 13, 2004 at 09:25:01AM -0500, Barnes, John wrote: > Has anyone see this alert? > > http://www.securityfocus.com/archive/1/353352 See for information on the FreeBSD XFree86 package. > It seems to work on Linux, but when I tried the proof of concept on > 4.3.0,1 running 5.2 RELEASE, I couldn't get the X server to core dump > or segmentation fault. So, it seems likely to me that FreeBSD is not > vulnerable to this. Any other thoughts on this matter? I cannot speculate as to why ``the proof of concept'' didn't work for you. Likely an error in ``the proof of concept'', whatever it is. All versions of XFree86 on all platforms are vulnerable. Furthermore, it seems that many other X11R6-based servers are vulnerable, as the bug goes way back. It is a very simple `strcpy' buffer overflow. Cheers, -- Jacques Vidrine / nectar@celabo.org / jvidrine@verio.net / nectar@freebsd.org