From: Julien Olivain <ju.o@free.fr>
To: Akhilesh Nema <nemaakhilesh@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/socat: security bump to version 1.8.0.2
Date: Sun, 02 Feb 2025 12:30:09 +0100 [thread overview]
Message-ID: <9cff407828cace45062069f517066940@free.fr> (raw)
In-Reply-To: <20250202002102.44367-1-nemaakhilesh@gmail.com>
On 02/02/2025 01:21, Akhilesh Nema wrote:
> It fixes an arbitrary file overwrite vulnerability in the readline.sh.
> (CVE-2024-54661)
>
> see - http://www.dest-unreach.org/socat/contrib/socat-secadv9.html
>
> README hash changed due to version update.
>
> Signed-off-by: Akhilesh Nema <nemaakhilesh@gmail.com>
I applied to master, thanks.
I also added the comment from Baruch that Buildroot is not directly
impacted.
Best regards,
Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-02-02 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-02 0:21 [Buildroot] [PATCH 1/1] package/socat: security bump to version 1.8.0.2 Akhilesh Nema
2025-02-02 5:38 ` Baruch Siach via buildroot
2025-02-02 11:30 ` Julien Olivain [this message]
2025-02-02 22:28 ` Peter Korsgaard
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=9cff407828cace45062069f517066940@free.fr \
--to=ju.o@free.fr \
--cc=buildroot@buildroot.org \
--cc=nemaakhilesh@gmail.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.