From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Update of openssh due to CVE CVE-2024-6387
Date: Mon, 01 Jul 2024 17:40:08 +0200 [thread overview]
Message-ID: <f8d04d52-323c-4b55-9176-2fa2fa658990@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 516 bytes --]
Hi All,
Openssh has a CVE
https://community.ipfire.org/t/cve-2024-6387-openssh-regession/11806
I am building a package update for Openssh to 9.8p1 and will submit to go into CU187.
I am not sure that it is super critical for IPFire as so far the exploit has only been demonstrated in 32 bit systems with the attacker having to try and make connections for 6 to 8 hours.
On 64 bit systems they expect it will take longer but so far the exploit has not yet been demonstrated.
Regards,
Adolf.
reply other threads:[~2024-07-01 15:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f8d04d52-323c-4b55-9176-2fa2fa658990@ipfire.org \
--to=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