From: Willy Tarreau <w@1wt.eu>
To: Kees Cook <keescook@chromium.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andy Lutomirski <luto@kernel.org>,
Michal Hocko <mhocko@kernel.org>,
Ben Hutchings <ben@decadent.org.uk>,
Hugh Dickins <hughd@google.com>, Oleg Nesterov <oleg@redhat.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>,
Rik van Riel <riel@redhat.com>,
Larry Woodman <lwoodman@redhat.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Tony Luck <tony.luck@intel.com>,
"James E.J. Bottomley" <jejb@parisc-linux.org>,
Helge Diller <deller@gmx.de>,
James Hogan <james.hogan@imgtec.com>,
Laura Abbott <labbott@redhat.com>, Greg KH <greg@kroah.com>,
"security@kernel.org" <security@kernel.org>,
Qualys Security Advisory <qsa@qualys.com>,
LKML <linux-kernel@vger.kernel.org>,
Ximin Luo <infinity0@debian.org>
Subject: Re: [RFC][PATCH] exec: Use init rlimits for setuid exec
Date: Thu, 6 Jul 2017 07:47:31 +0200 [thread overview]
Message-ID: <20170706054731.GB25439@1wt.eu> (raw)
In-Reply-To: <20170706043235.GA36170@beast>
On Wed, Jul 05, 2017 at 09:32:35PM -0700, Kees Cook wrote:
> In an attempt to provide sensible rlimit defaults for setuid execs, this
> inherits the namespace's init rlimits:
>
> $ ulimit -s
> 8192
> $ ulimit -s unlimited
> $ /bin/sh -c 'ulimit -s'
> unlimited
> $ sudo /bin/sh -c 'ulimit -s'
> 8192
>
> This is modified from Brad Spengler/PaX Team's hard-coded setuid exec
> stack rlimit (8MB) in the last public patch of grsecurity/PaX based on
> my understanding of the code. Changes or omissions from the original
> code are mine and don't reflect the original grsecurity/PaX code.
>
> Signed-off-by: Kees Cook <keescook@chromium.org>
> ---
> Instead of copying all rlimits, we could also pick specific ones to copy
> (e.g. RLIMIT_STACK, or ones from Andy's list) or exclude from copying
> (probably better to blacklist than whitelist).
>
> I think this is the right way to find the ns init task, but maybe it
> needs locking?
> ---
> fs/exec.c | 34 ++++++++++++++++++++++++++++++----
> 1 file changed, 30 insertions(+), 4 deletions(-)
>
> diff --git a/fs/exec.c b/fs/exec.c
> index 904199086490..80e8b2bd4284 100644
> --- a/fs/exec.c
> +++ b/fs/exec.c
> @@ -1675,6 +1675,12 @@ static int exec_binprm(struct linux_binprm *bprm)
> return ret;
> }
>
> +static inline bool is_setuid_exec(struct linux_binprm *bprm)
> +{
> + return (!uid_eq(bprm->cred->euid, current_euid()) ||
> + !gid_eq(bprm->cred->egid, current_egid()));
> +}
> +
> /*
> * sys_execve() executes a new program.
> */
> @@ -1687,6 +1693,7 @@ static int do_execveat_common(int fd, struct filename *filename,
> struct linux_binprm *bprm;
> struct file *file;
> struct files_struct *displaced;
> + struct rlimit saved_rlim[RLIM_NLIMITS];
> int retval;
>
> if (IS_ERR(filename))
> @@ -1771,24 +1778,38 @@ static int do_execveat_common(int fd, struct filename *filename,
> if (retval < 0)
> goto out;
>
> + /*
> + * From here forward, we've got credentials set up and we're
> + * using resources, so do rlimit replacement before we start
> + * copying strings. (Note that the RLIMIT_NPROC check has
> + * already happened.)
> + */
> + BUILD_BUG_ON(sizeof(saved_rlim) != sizeof(current->signal->rlim));
> + if (is_setuid_exec(bprm)) {
> + memcpy(saved_rlim, current->signal->rlim, sizeof(saved_rlim));
> + memcpy(current->signal->rlim,
> + task_active_pid_ns(current)->child_reaper->signal->rlim,
> + sizeof(current->signal->rlim));
> + }
> +
But you're not replacing just RLIMIT_STACK but all rlimits here. Please
don't do this, as I mentionned elsewhere in the thread it will really
become a pain at least for RLIMIT_CORE and RLIMIT_NOFILE. Better only
apply RLIMIT_STACK as the commit message mentions it.
Willy
next prev parent reply other threads:[~2017-07-06 5:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 4:32 Kees Cook
2017-07-06 4:59 ` Andy Lutomirski
2017-07-06 12:45 ` Eric W. Biederman
2017-07-06 15:27 ` Andy Lutomirski
2017-07-06 5:47 ` Willy Tarreau [this message]
2017-07-06 12:38 ` Eric W. Biederman
2017-07-06 15:30 ` Andy Lutomirski
2017-07-06 16:34 ` Linus Torvalds
2017-07-06 16:50 ` Linus Torvalds
2017-07-06 17:29 ` Kees Cook
2017-07-06 17:52 ` Linus Torvalds
2017-07-06 19:12 ` Kees Cook
2017-07-07 4:48 ` Andy Lutomirski
2017-07-07 5:03 ` Linus Torvalds
2017-07-07 5:10 ` Kees Cook
2017-07-07 5:15 ` Kees Cook
2017-07-07 5:36 ` Andy Lutomirski
2017-07-07 5:45 ` Kees Cook
2017-07-07 6:02 ` Linus Torvalds
2017-07-07 6:10 ` Kees Cook
2017-07-07 16:06 ` Linus Torvalds
2017-07-07 18:28 ` Kees Cook
2017-07-07 14:48 ` Andy Lutomirski
2017-07-07 5:39 ` Linus Torvalds
2017-07-07 5:49 ` Kees Cook
2017-07-07 6:40 ` Kees Cook
2017-07-07 16:22 ` Linus Torvalds
2017-07-07 18:27 ` Kees Cook
2017-07-10 8:44 ` Michal Hocko
2017-07-10 16:12 ` Kees Cook
2017-07-10 16:18 ` Linus Torvalds
2017-07-10 16:52 ` Willy Tarreau
2017-07-10 16:27 ` Michal Hocko
2017-07-10 18:16 ` Michal Hocko
2017-07-10 18:29 ` Rik van Riel
2017-07-12 23:50 ` Alan Cox
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=20170706054731.GB25439@1wt.eu \
--to=w@1wt.eu \
--cc=Jason@zx2c4.com \
--cc=ben@decadent.org.uk \
--cc=deller@gmx.de \
--cc=greg@kroah.com \
--cc=hughd@google.com \
--cc=infinity0@debian.org \
--cc=james.hogan@imgtec.com \
--cc=jejb@parisc-linux.org \
--cc=keescook@chromium.org \
--cc=kirill@shutemov.name \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=lwoodman@redhat.com \
--cc=mhocko@kernel.org \
--cc=oleg@redhat.com \
--cc=qsa@qualys.com \
--cc=riel@redhat.com \
--cc=security@kernel.org \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®