From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libopenssl: security bump to v1.1.1g
Date: Tue, 21 Apr 2020 22:29:54 +0200 [thread overview]
Message-ID: <20200421222954.3781cc2a@windsurf.home> (raw)
In-Reply-To: <20200421133651.6921-1-titouan.christophe@railnova.eu>
On Tue, 21 Apr 2020 15:36:51 +0200
Titouan Christophe <titouan.christophe@railnova.eu> wrote:
> This fixes CVE-2020-1967:
> Server or client applications that call the SSL_check_chain() function during
> or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a
> result of incorrect handling of the "signature_algorithms_cert" TLS extension.
> The crash occurs if an invalid or unrecognised signature algorithm is received
> from the peer. This could be exploited by a malicious peer in a Denial of
> Service attack. OpenSSL version 1.1.1d, 1.1.1e, and 1.1.1f are affected by this
> issue. This issue did not affect OpenSSL versions prior to 1.1.1d.
>
> See https://www.openssl.org/news/secadv/20200421.txt
>
> Also update the hash file to the new two spaces convention
>
> Signed-off-by: Titouan Christophe <titouan.christophe@railnova.eu>
> ---
> package/libopenssl/libopenssl.hash | 6 +++---
> package/libopenssl/libopenssl.mk | 2 +-
> 2 files changed, 4 insertions(+), 4 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-04-21 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 13:36 [Buildroot] [PATCH 1/1] package/libopenssl: security bump to v1.1.1g Titouan Christophe
2020-04-21 20:29 ` Thomas Petazzoni [this message]
2020-05-06 14:33 ` Johan Derycke
2020-05-07 21:57 ` Peter Korsgaard
2020-05-07 21:56 ` 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=20200421222954.3781cc2a@windsurf.home \
--to=thomas.petazzoni@bootlin.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