[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 14 Jul 2011 11:27:51 +1000
From: NeilBrown <neilb@...e.de>
To: James Morris <jmorris@...ei.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Solar Designer <solar@...nwall.com>,
Vasiliy Kulikov <segoon@...nwall.com>, linux-kernel@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...e.de>,
Andrew Morton <akpm@...ux-foundation.org>,
"David S. Miller" <davem@...emloft.net>,
kernel-hardening@...ts.openwall.com, Jiri Slaby <jslaby@...e.cz>,
Alexander Viro <viro@...iv.linux.org.uk>,
linux-fsdevel@...r.kernel.org,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Eric Paris <eparis@...hat.com>, Stephen Smalley <sds@...ho.nsa.gov>
Subject: Re: [PATCH] move RLIMIT_NPROC check from set_user() to
do_execve_common()
On Thu, 14 Jul 2011 10:11:57 +1000 (EST) James Morris <jmorris@...ei.org>
wrote:
> On Wed, 13 Jul 2011, Linus Torvalds wrote:
>
> > It sounds like people are effectively Ack'ing the patch, but with this
> > kind of patch I don't want to add the "implicit Ack" that I often do
> > for regular stuff.
> >
> > So could people who think that the patch is ok in its current form
> > just send me their acked-by or reviewed-by? I haven't heard any actual
> > objection to it, and I think it's valid for the current -rc.
> >
> > Alternatively, feel free to send a comment like "I think it's the
> > right thing, but maybe it should wait for the next merge window"..
>
> Count me in the latter.
>
> It does look ok to me, but I'd be happier if it had more testing first (in
> -mm perhaps). I think some security folk may be on summer vacation, too.
>
>
> - James
I'm still trying to understand the full consequences, but I agree that there
is no rush - the code has been this way for quite a while and their is no
obvious threat that would expedite things (as far as I know).
However I'm not convinced that testing will help all that much - if there are
problems they will be is rare corner cases that testing is unlikely to find.
The only case where this change will improve safety is where:
1/ a process has RLIMIT_NPROC set
2/ the process is running with root privileges
3/ the process calls setuid() and doesn't handle errors.
I think the only times that a root process would have RLIMIT_NPROC set are:
1/ if it explicitly set up rlimits before calling setuid. In this case
we should be able to expect that the process checks setuid .. maybe
this is naive(?)
2/ if the process was setuid-root and inherited rlimits from before, and
never re-set them. In this case it is easy to imagine that a setuid()
would not be checked.
So maybe an alternate 'fix' would be to reset all rlimits to match init_task
when a setuid-root happens. There are other corner cases where inappropriate
rlimits can cause setuid programs to behave in ways they don't expect.
Obviously such programs are buggy, but so are programs that don't check
'setuid'. (There is a CVE about mount potentially corrupting mtab.)
... maybe that would introduce other problems though.
In short: while I don't feel bold enough to 'nack' this patch, I don't really
feel comfortable enough to 'ack' it either.
NeilBrown
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
