From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/wolfssl: security bump to version 3.5.17
Date: Fri, 25 Jan 2019 08:36:45 +0100 [thread overview]
Message-ID: <87y3799oj6.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190116124521.17109-1-peter@korsgaard.com> (Peter Korsgaard's message of "Wed, 16 Jan 2019 13:45:21 +0100")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> From the release notes:
> This release of wolfSSL includes a fix for 1 security vulnerability.
> Medium level fix for potential cache attack with a variant of
> Bleichenbacher?s attack. Earlier versions of wolfSSL leaked PKCS #1 v1.5
> padding information during private key decryption that could lead to a
> potential padding oracle attack. It is recommended that users update to the
> latest version of wolfSSL if they have RSA cipher suites enabled and have
> the potential for malicious software to be ran on the same system that is
> performing RSA operations. Users that have only ECC cipher suites enabled
> and are not performing RSA PKCS #1 v1.5 Decryption operations are not
> vulnerable. Also users with TLS 1.3 only connections are not vulnerable to
> this attack. Thanks to Eyal Ronen (Weizmann Institute), Robert Gillham
> (University of Adelaide), Daniel Genkin (University of Michigan), Adi Shamir
> (Weizmann Institute), David Wong (NCC Group), and Yuval Yarom (University of
> Adelaide and Data61) for the report.
> The paper for further reading on the attack details can be found at
> http://cat.eyalro.net/cat.pdf
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed to 2018.02.x and 2018.11.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2019-01-25 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 12:45 [Buildroot] [PATCH] package/wolfssl: security bump to version 3.5.17 Peter Korsgaard
2019-01-16 15:38 ` Peter Korsgaard
2019-01-25 7:36 ` 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=87y3799oj6.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