From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Christian Stewart via buildroot <buildroot@buildroot.org>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH 1/1] package/runc: security bump to v1.1.2
Date: Wed, 1 Jun 2022 23:14:48 +0200 [thread overview]
Message-ID: <20220601231448.0a0109c0@windsurf> (raw)
In-Reply-To: <20220601181047.89675-1-christian@paral.in>
On Wed, 1 Jun 2022 11:10:47 -0700
Christian Stewart via buildroot <buildroot@buildroot.org> wrote:
> Fixes CVE-2022-29162
>
> Minor security issue (which appears to not be exploitable) related to process
> capabilities.
>
> A bug was found in runc where runc exec --cap executed processes with ble Linux
> process capabilities, creating an atypical Linux environment. For more
> information, see GHSA-f3fp-gc8g-vw66 and CVE-2022-29162.
>
> runc spec no longer sets any inheritable capabilities in the created example OCI
> spec (config.json) file.
>
> https://github.com/opencontainers/runc/releases/tag/v1.1.2
>
> Signed-off-by: Christian Stewart <christian@paral.in>
> ---
> package/runc/runc.hash | 2 +-
> package/runc/runc.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-06-01 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 18:10 [Buildroot] [PATCH 1/1] package/runc: security bump to v1.1.2 Christian Stewart via buildroot
2022-06-01 21:14 ` Thomas Petazzoni via buildroot [this message]
2022-06-07 13:59 ` 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=20220601231448.0a0109c0@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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