From: Michael Tremer <michael.tremer@ipfire.org>
To: Adolf Belka <adolf.belka@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: Strongswan 6.0.3 update with CVE fix
Date: Thu, 6 Nov 2025 20:19:21 +0000 [thread overview]
Message-ID: <0978596A-770B-433D-A955-7234A537A380@ipfire.org> (raw)
In-Reply-To: <00a79390-d15d-48ee-9b47-f15b48c7b358@ipfire.org>
Hello Adolf,
Yes, this is good thing to do.
The vulnerability reads as this:
Fixed a vulnerability in the eap-mschapv2 plugin related to processing Failure Request packets on the client that can lead to a heap-based buffer overflow and potentially remote code execution. This vulnerability has been registered as CVE-2025-62291. Please refer to our blog for details.
So it would not affect us as we are not using this plugin, but we should update regardless.
Best,
-Michael
> On 6 Nov 2025, at 19:46, Adolf Belka <adolf.belka@ipfire.org> wrote:
>
> Hi all,
>
> I have found that there is a new strongswan update that has a CVE fix in it.
>
> I will also do an update for that after the suricata update has been submitted.
>
> Regards,
>
> Adolf.
>
>
prev parent reply other threads:[~2025-11-06 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 19:46 Adolf Belka
2025-11-06 20:19 ` Michael Tremer [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=0978596A-770B-433D-A955-7234A537A380@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=adolf.belka@ipfire.org \
--cc=development@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox