From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: Re: 01/01: gnu: dropbear: Update to 2016.74 [security fixes].
Date: Sun, 14 Aug 2016 16:21:59 -0400 [thread overview]
Message-ID: <20160814202159.GA15698@jasmine> (raw)
In-Reply-To: <20160814201919.D319F2200FE@vcs.savannah.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 <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
parent reply other threads:[~2016-08-14 20:22 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20160814201919.D319F2200FE@vcs.savannah.gnu.org>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160814202159.GA15698@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).