From: "chunhui.jia" <chunhui.jia@linux.intel.com>
To: "Brad Bishop" <bradleyb@fuzziesquirrel.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: openssl upgrade
Date: Thu, 07 May 2020 15:43:19 +0800 [thread overview]
Message-ID: <5EB3BC15.60402@linux.intel.com> (raw)
In-Reply-To: <FAD2D9A0-A730-4A28-9798-0B8B3228E14F@fuzziesquirrel.com>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
Brad,
There is a CVE reported in openSSL 1.1.1d (used by current openbmc). Severity is high.
CVE-2020-1967 https://nvd.nist.gov/vuln/detail/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. Fixed in OpenSSL 1.1.1g (Affected 1.1.1d-1.1.1f).
It is fixed in 1.1.1g. Upstream recipe already point openssl to latest version (1.1.1g).
https://git.yoctoproject.org/cgit.cgi/poky/plain/meta/recipes-connectivity/openssl/openssl_1.1.1g.bb
Will you update poky subtree to latest?
[-- Attachment #2: Type: text/html, Size: 5690 bytes --]
next prev parent reply other threads:[~2020-05-07 7:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 2:25 OpenBMC CVE issues in openssl Wang, Kuiying
2019-09-24 2:41 ` Brad Bishop
2019-09-24 2:48 ` Wang, Kuiying
2019-09-24 11:11 ` Brad Bishop
2019-09-25 1:22 ` Wang, Kuiying
2020-05-07 7:43 ` chunhui.jia [this message]
2020-05-07 16:54 ` openssl upgrade CVE-2020-1967 Joseph Reynolds
2020-05-08 0:27 ` chunhui.jia
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=5EB3BC15.60402@linux.intel.com \
--to=chunhui.jia@linux.intel.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=openbmc@lists.ozlabs.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.