From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Sergio Prado <sergio.prado@e-labworks.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/wolfssl: security bump to version 5.4.0
Date: Thu, 15 Sep 2022 00:14:58 +0200 [thread overview]
Message-ID: <87o7vhob6l.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220808081141.582053-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Mon, 8 Aug 2022 10:11:41 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> Fix the following vulnerabilities:
> - [High] Potential for DTLS DoS attack. In wolfSSL versions before
> 5.4.0 the return-routability check is wrongly skipped in a specific
> edge case. The check on the return-routability is there for stopping
> attacks that either consume excessive resources on the server, or try
> to use the server as an amplifier sending an excessive amount of
> messages to a victim IP. If using DTLS 1.0/1.2 on the server side
> users should update to avoid the potential DoS attack. CVE-2022-34293
> - [Medium] Ciphertext side channel attack on ECC and DH operations.
> Users on systems where rogue agents can monitor memory use should
> update the version of wolfSSL and change private ECC keys.
> https://github.com/wolfSSL/wolfssl/releases/tag/v5.4.0-stable
> https://www.wolfssl.com/docs/security-vulnerabilities/
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2022.05.x and 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-09-14 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 8:11 [Buildroot] [PATCH 1/1] package/wolfssl: security bump to version 5.4.0 Fabrice Fontaine
2022-08-08 20:49 ` Thomas Petazzoni via buildroot
2022-09-14 22:14 ` 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=87o7vhob6l.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=sergio.prado@e-labworks.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 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.