From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] dropbear: security bump to version 2017.75
Date: Thu, 01 Jun 2017 16:03:58 +0200 [thread overview]
Message-ID: <87wp8vls8h.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170520151548.23594-1-peter@korsgaard.com> (Peter Korsgaard's message of "Sat, 20 May 2017 17:15:48 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes:
> - CVE-2017-9078: A double-free in the server could be triggered by an
> authenticated user if dropbear is running with -a (Allow connections to
> forwarded ports from any host) This could potentially allow arbitrary code
> execution as root by an authenticated user. Affects versions 2013.56 to
> 2016.74. Thanks to Mark Shepard for reporting the crash.
> - CVE-2017-9079: Dropbear parsed authorized_keys as root, even if it were a
> symlink. The fix is to switch to user permissions when opening
> authorized_keys.
> A user could symlink their ~/.ssh/authorized_keys to a root-owned file
> they couldn't normally read. If they managed to get that file to contain
> valid authorized_keys with command= options it might be possible to read
> other contents of that file. This information disclosure is to an already
> authenticated user. Thanks to Jann Horn of Google Project Zero for
> reporting this.
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed to 2017.02.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-06-01 14:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 15:15 [Buildroot] [PATCH] dropbear: security bump to version 2017.75 Peter Korsgaard
2017-05-21 21:32 ` Peter Korsgaard
2017-06-01 14:03 ` Peter Korsgaard [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wp8vls8h.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox