Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/openssh: security bump to version 8.6p1
Date: Mon, 17 May 2021 23:32:22 +0200	[thread overview]
Message-ID: <87im3hgi6x.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210515121035.2395250-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sat, 15 May 2021 14:10:35 +0200")

>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:

 > Security
 > ========

 >  * sshd(8): OpenSSH 8.5 introduced the LogVerbose keyword. When this
 >    option was enabled with a set of patterns that activated logging
 >    in code that runs in the low-privilege sandboxed sshd process, the
 >    log messages were constructed in such a way that printf(3) format
 >    strings could effectively be specified the low-privilege code.

 >    An attacker who had sucessfully exploited the low-privilege
 >    process could use this to escape OpenSSH's sandboxing and attack
 >    the high-privilege process. Exploitation of this weakness is
 >    highly unlikely in practice as the LogVerbose option is not
 >    enabled by default and is typically only used for debugging. No
 >    vulnerabilities in the low-privilege process are currently known
 >    to exist.

 > https://www.openssh.com/txt/release-8.6

 > Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

Committed to 2021.02.x, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2021-05-17 21:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-15 12:10 [Buildroot] [PATCH 1/1] package/openssh: security bump to version 8.6p1 Fabrice Fontaine
2021-05-15 15:19 ` Yann E. MORIN
2021-05-17 21:32 ` 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=87im3hgi6x.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