Re: 01/01: gnu: dropbear: Update to 2016.74 [security fixes].

Re: 01/01: gnu: dropbear: Update to 2016.74 [security fixes].

[Leo Famulari]

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 <leo@famulari.name>
> 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