From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: "Jérôme Pouiller" <jezz@sysmic.org>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/strongswan: security bump to version 5.9.8
Date: Mon, 14 Nov 2022 16:40:44 +0100 [thread overview]
Message-ID: <874jv1lf2b.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20221104161851.645974-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Fri, 4 Nov 2022 17:18:51 +0100")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> Fixed a vulnerability related to online certificate revocation checking
> that was caused because the revocation plugin used potentially untrusted
> OCSP URIs and CRL distribution points in certificates. This allowed a
> remote attacker to initiate IKE_SAs and send crafted certificates that
> contain URIs pointing to servers under their control, which could have
> lead to a denial-of-service attack. This vulnerability has been
> registered as CVE-2022-40617.
> Drop patch (already in version)
> https://www.strongswan.org/blog/2022/10/03/strongswan-vulnerability-(cve-2022-40617).html
> https://github.com/strongswan/strongswan/releases/tag/5.9.6
> https://github.com/strongswan/strongswan/releases/tag/5.9.7
> https://github.com/strongswan/strongswan/releases/tag/5.9.8
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2022.08.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-11-14 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 16:18 [Buildroot] [PATCH 1/1] package/strongswan: security bump to version 5.9.8 Fabrice Fontaine
2022-11-05 20:03 ` Thomas Petazzoni via buildroot
2022-11-14 15:40 ` 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=874jv1lf2b.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
--cc=jezz@sysmic.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.