From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Marek Vasut <marex@denx.de>,
steve@sakoman.com, openembedded-core@lists.openembedded.org
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH] ncurses: Mitigate CVE-2023-29491
Date: Mon, 09 Oct 2023 17:44:11 +0100 [thread overview]
Message-ID: <4eb39033effcbbcd8651f73632b94bb159fecb65.camel@linuxfoundation.org> (raw)
In-Reply-To: <20231009163110.94431-1-marex@denx.de>
On Mon, 2023-10-09 at 18:31 +0200, Marek Vasut wrote:
> Configure with "--disable-root-environ" to disallow loading of
> custom terminfo entries in setuid/setgid programs, mitigating the
> impact of CVE-2023-29491.
>
> This is taken from debian:
> https://salsa.debian.org/debian/ncurses/-/commit/1c530aad772f7aeef039b8780d51cd09bd5a08ac
>
> Signed-off-by: Marek Vasut <marex@denx.de>
> ---
> Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>
> Cc: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
> meta/recipes-core/ncurses/ncurses.inc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/recipes-core/ncurses/ncurses.inc b/meta/recipes-core/ncurses/ncurses.inc
> index 367f3b19f4..1bc07ec2d4 100644
> --- a/meta/recipes-core/ncurses/ncurses.inc
> +++ b/meta/recipes-core/ncurses/ncurses.inc
> @@ -87,6 +87,7 @@ ncurses_configure() {
> --enable-sigwinch \
> --enable-pc-files \
> --disable-rpath-hack \
> + --disable-root-environ \
> ${EXCONFIG_ARGS} \
> --with-manpage-format=normal \
> --without-manpage-renames \
Should the patch add a CVE_STATUS entry as well so the cve tooling can
tell we've mitigated this?
Cheers,
Richard
next prev parent reply other threads:[~2023-10-09 16:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 16:31 [PATCH] ncurses: Mitigate CVE-2023-29491 Marek Vasut
2023-10-09 16:44 ` Richard Purdie [this message]
2023-10-09 16:51 ` [OE-core] " Marko, Peter
2023-10-09 16:56 ` Marek Vasut
2023-10-09 17:27 ` Marko, Peter
2023-10-09 19:27 ` Marek Vasut
2023-10-09 20:56 ` Marko, Peter
2023-10-09 19:30 ` Marek Vasut
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=4eb39033effcbbcd8651f73632b94bb159fecb65.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alexandre.belloni@bootlin.com \
--cc=marex@denx.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=steve@sakoman.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox