From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 47229@debbugs.gnu.org
Subject: bug#47229: Local privilege escalation via guix-daemon and ‘--keep-failed’
Date: Thu, 18 Mar 2021 17:10:49 -0400 [thread overview]
Message-ID: <YFPB2RTVkRxx8sfk@jasmine.lan> (raw)
In-Reply-To: <87lfaksock.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
On Thu, Mar 18, 2021 at 12:17:15PM +0100, Ludovic Courtès wrote:
> It does not affect multi-user setups where ‘guix-daemon’ runs on a
> separate machine and is accessed over the network, via
> ‘GUIX_DAEMON_SOCKET’, as is customary on cluster setups. Machines where
> the Linux “protected hardlink”[*] feature is enabled, which is common,
> are also unaffected—this is the case when the contents of
> /proc/sys/fs/protected_hardlinks are 1.
After publishing the advisory, we received a clarification about the
impact of "protected hardlinks".
When using a guix-daemon that does not include the fix [0] for the bug
reported here, it is still possible for rogue build scripts to escape
the build environment, even when protected hardlinks are enabled.
Protected hardlinks do make exploitation significantly more difficult,
but not impossible.
For this reason, we continue to recommend that all Guix users upgrade
their guix-daemons, as described in the original advisory.
[0]
https://git.savannah.gnu.org/cgit/guix.git/commit/?id=ec7fb669945bfb47c5e1fdf7de3a5d07f7002ccf
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-03-18 21:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 11:17 bug#47229: Local privilege escalation via guix-daemon and ‘--keep-failed’ Ludovic Courtès
2021-03-18 11:45 ` Ludovic Courtès
2021-03-18 13:14 ` Ludovic Courtès
2021-03-18 11:53 ` Léo Le Bouter via Bug reports for GNU Guix
2021-03-18 21:10 ` Leo Famulari [this message]
2021-04-10 17:56 ` Leo Famulari
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=YFPB2RTVkRxx8sfk@jasmine.lan \
--to=leo@famulari.name \
--cc=47229@debbugs.gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.