From owner-freebsd-security@FreeBSD.ORG Sun Apr 20 19:00:30 2014 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5269557D for ; Sun, 20 Apr 2014 19:00:30 +0000 (UTC) Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1A1AD19AE for ; Sun, 20 Apr 2014 19:00:30 +0000 (UTC) Received: by mail-ob0-f173.google.com with SMTP id wn1so3542065obc.18 for ; Sun, 20 Apr 2014 12:00:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=JonhdtaXm6bnLkksht+/51A44wRNA/gdmLb1FGNih9w=; b=Oa9zbxlsmhzdmXsb2OMz4s1j7f/hHwvPSz61ZmUyXivxcijQ5TyUpYP77kxCMpKj2O ko7gIX7G8+NAjLh10rtn6A2s8tBTPK3uGZdR98OObKuLtSbJWuFnpJFUw95VRgCdPqnK U1RBKy3dUDL5vslQbdsENIpMckDH5MM6ujlLfF1NZjBisikD+721ANT7Z6yl3AXL0AF9 iRjuUKVslxpED211s6UrRPHATawWdQq4gGHdHSy2yBaL63VR8PCEmtl0G18TFR7NvYHL EXb0q/gaSPY3Z+ExtmV2fktQlahClM4TtM0rvlLaoC4DbdOQyOyWhtwMsZwABsGI9ReA w4OA== MIME-Version: 1.0 X-Received: by 10.182.87.42 with SMTP id u10mr27769156obz.22.1398020428859; Sun, 20 Apr 2014 12:00:28 -0700 (PDT) Sender: ndorfman@gmail.com Received: by 10.60.158.106 with HTTP; Sun, 20 Apr 2014 12:00:28 -0700 (PDT) In-Reply-To: <201404201831.s3KIVCSY054778@catnip.dyslexicfish.net> References: <534B11F0.9040400@paladin.bulgarpress.com> <201404141207.s3EC7IvT085450@chronos.org.uk> <201404141232.s3ECWFQ1081178@catnip.dyslexicfish.net> <53522186.9030207@FreeBSD.org> <201404200548.s3K5mV7N055244@catnip.dyslexicfish.net> <53540307.1070708@quietfountain.com> <201404201831.s3KIVCSY054778@catnip.dyslexicfish.net> Date: Sun, 20 Apr 2014 15:00:28 -0400 X-Google-Sender-Auth: Vsn6LrzhY_o-Av9CO9S7T0PYawI Message-ID: Subject: Re: De Raadt + FBSD + OpenSSH + hole? From: Nathan Dorfman To: Jamie Landeg-Jones Content-Type: text/plain; charset=UTF-8 Cc: hcoin@quietfountain.com, freebsd-security@freebsd.org X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Apr 2014 19:00:30 -0000 On Sun, Apr 20, 2014 at 2:31 PM, Jamie Landeg-Jones wrote: > Once memory has been freed, I thought any attempt by a user process to > access it would cause a SIGSEV. > > I thought the issue was with programs that inadvertantly expose (either > to read or write) other parts of their active memory. > > Of course, if a process rolls it's own in-process implementation > of malloc/free, then this point is moot, but once you free memory back > to the system, isn't in no longer accessable anyway? free() doesn't usually "free memory back to the system." It just puts it back onto a "free list" managed by libc, entirely within the process's address space. "Use after free" is actually a rather common type of bug -- do a web search on that term to see just how often it comes up. -nd.