From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/libssh: security bump to version 0.9.6
Date: Mon, 13 Sep 2021 22:37:08 +0200 [thread overview]
Message-ID: <87lf40w6tn.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210912165643.2170239-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sun, 12 Sep 2021 18:56:43 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> Fix CVE-2021-3634: A flaw has been found in libssh in versions prior to
> 0.9.6. The SSH protocol keeps track of two shared secrets during the
> lifetime of the session. One of them is called secret_hash and the other
> session_id. Initially, both of them are the same, but after key
> re-exchange, previous session_id is kept and used as an input to new
> secret_hash. Historically, both of these buffers had shared length
> variable, which worked as long as these buffers were same. But the key
> re-exchange operation can also change the key exchange method, which can
> be based on hash of different size, eventually creating "secret_hash" of
> different size than the session_id has. This becomes an issue when the
> session_id memory is zeroed or when it is used again during second key
> re-exchange.
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-09-14 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-12 16:56 [Buildroot] [PATCH 1/1] package/libssh: security bump to version 0.9.6 Fabrice Fontaine
2021-09-13 20:37 ` Peter Korsgaard [this message]
2021-09-14 12:13 ` Peter Korsgaard
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=87lf40w6tn.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
/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