From owner-freebsd-bugs@freebsd.org  Thu Dec 29 22:23:49 2016
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1167EC96AB2
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Thu, 29 Dec 2016 22:23:49 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 00DCF169E
 for <freebsd-bugs@FreeBSD.org>; Thu, 29 Dec 2016 22:23:49 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id uBTMNm1G003361
 for <freebsd-bugs@FreeBSD.org>; Thu, 29 Dec 2016 22:23:48 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 213922] crafted data could cause qsort to exhaust stack space
Date: Thu, 29 Dec 2016 22:23:48 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: CURRENT
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: pfg@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-213922-8-hoCAGRVEEv@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-213922-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-213922-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Dec 2016 22:23:49 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213922

--- Comment #4 from Pedro F. Giffuni <pfg@FreeBSD.org> ---
(In reply to jhoward from comment #3)

Thanks for looking into it. I have just been too busy. BTW, if you could up=
load
a diff to bugzilla it would be much better.

You can check the standalone tests here:
https://svnweb.freebsd.org/base/stable/9/tools/regression/lib/libc/stdlib/

(Newer FreeBSD versions have integrated the regression tool into the
testsuite.) I think I had a random testcase with more datapoints somewhere =
to
verify the last commit.

and you can get VM images from ftp, for example here:
ftp://ftp.freebsd.org/pub/FreeBSD/releases/VM-IMAGES/11.0-RELEASE/

About exploitability, it very much depends on where qsort() is used, opengr=
ok
is your friend, and if you are able to realistically generate such sequence=
. I
am aware there are cases where the algorithm can be suboptimal; it may be t=
he
case that the algorithm needs revision (I just haven't seen a case in real
life).

--=20
You are receiving this mail because:
You are the assignee for the bug.=