From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: 01/01: gnu: dropbear: Update to 2016.74 [security fixes]. Date: Sun, 14 Aug 2016 16:21:59 -0400 Message-ID: <20160814202159.GA15698@jasmine> References: <20160814201919.14838.65503@vcs.savannah.gnu.org> <20160814201919.D319F2200FE@vcs.savannah.gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46580) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bZ1vD-0005uW-Bo for guix-devel@gnu.org; Sun, 14 Aug 2016 16:22:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bZ1v8-0001CY-8t for guix-devel@gnu.org; Sun, 14 Aug 2016 16:22:14 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:43070) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bZ1v6-0001Bh-VI for guix-devel@gnu.org; Sun, 14 Aug 2016 16:22:10 -0400 Received: from localhost (c-68-81-58-201.hsd1.pa.comcast.net [68.81.58.201]) by mail.messagingengine.com (Postfix) with ESMTPA id E5C21F296E for ; Sun, 14 Aug 2016 16:22:00 -0400 (EDT) Content-Disposition: inline In-Reply-To: <20160814201919.D319F2200FE@vcs.savannah.gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org On Sun, Aug 14, 2016 at 08:19:19PM +0000, Leo Famulari wrote: > lfam pushed a commit to branch master > in repository guix. > > commit d4db0612dcfb3e19fc2be7447b1ee242819c0df8 > Author: Leo Famulari > Date: Sun Aug 14 16:16:40 2016 -0400 > > gnu: dropbear: Update to 2016.74 [security fixes]. > > * gnu/packages/ssh.scm (dropbear): Update to 2016.74. I just updated Drobpear to 2016.74. This update contains several bug fixes with security implications, including bugs that could allow arbitrary code execution. These bugs have not been assigned CVE IDs yet. Here is a quote from the release announcement [0]: 2016.74 - 21 July 2016 - Security: Message printout was vulnerable to format string injection. If specific usernames including "%" symbols can be created on a system (validated by getpwnam()) then an attacker could run arbitrary code as root when connecting to Dropbear server. A dbclient user who can control username or host arguments could potentially run arbitrary code as the dbclient user. This could be a problem if scripts or webpages pass untrusted input to the dbclient program. - Security: dropbearconvert import of OpenSSH keys could run arbitrary code as the local dropbearconvert user when parsing malicious key files - Security: dbclient could run arbitrary code as the local dbclient user if particular -m or -c arguments are provided. This could be an issue where dbclient is used in scripts. - Security: dbclient or dropbear server could expose process memory to the running user if compiled with DEBUG_TRACE and running with -v The security issues were reported by an anonymous researcher working with Beyond Security's SecuriTeam Secure Disclosure www.beyondsecurity.com/ssd.html - Fix port forwarding failure when connecting to domains that have both IPv4 and IPv6 addresses. The bug was introduced in 2015.68 - Fix 100% CPU use while waiting for rekey to complete. Thanks to Zhang Hui P for the patch [0] http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/2016q3/001932.html