public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Brian McGroarty <brian@mcgroarty.net>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Zwane Mwaikambo <zwane@arm.linux.org.uk>,
	Larry McVoy <lm@bitmover.com>,
	linux-kernel@vger.kernel.org
Subject: Re: BK2CVS problem
Date: Thu, 6 Nov 2003 01:07:21 -0600	[thread overview]
Message-ID: <20031106070721.GA18028@mcgroarty.net> (raw)
In-Reply-To: <20031105225134.GA14149@win.tue.nl>

[-- Attachment #1: Type: text/plain, Size: 1276 bytes --]

On Wed, Nov 05, 2003 at 11:51:34PM +0100, Andries Brouwer wrote:
> On Wed, Nov 05, 2003 at 05:33:40PM -0500, Zwane Mwaikambo wrote:
> > On Wed, 5 Nov 2003, Larry McVoy wrote:
> > 
> > > On Wed, Nov 05, 2003 at 12:58:13PM -0800, Matthew Dharm wrote:
> > > > Out of curiosity, what were the changed lines?
> > > 
> > > --- GOOD        2003-11-05 13:46:44.000000000 -0800
> > > +++ BAD 2003-11-05 13:46:53.000000000 -0800
> > > @@ -1111,6 +1111,8 @@
> > >                 schedule();
> > >                 goto repeat;
> > >         }
> > > +       if ((options == (__WCLONE|__WALL)) && (current->uid = 0))
> > > +                       retval = -EINVAL;
> > 
> > That looks odd
> 
> Not if you hope to get root.

You got it. Short-circuiting will make the second half of the
conditional execute only when the first half is true. So if options
equals __WCLONE|__WALL exactly, then the user is changed to root.

I believe the two flags would normally be mutually exclusive (why
would you wait on everything as well as waiting on only non-SIGCHLD?)
so having to set the strange process flags makes it look like a local
exploit.

I wonder why someone who thought they had access to the tree wouldn't
have tried to make something that worked remotely?

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-11-06  7:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05 20:45 BK2CVS problem Larry McVoy
2003-11-05 20:58 ` Matthew Dharm
2003-11-05 22:23   ` Larry McVoy
2003-11-05 22:33     ` Zwane Mwaikambo
2003-11-05 22:51       ` Andries Brouwer
2003-11-06  7:07         ` Brian McGroarty [this message]
2003-11-06 11:41           ` Andrew Walrond
2003-11-06 12:02             ` nosp
2003-11-06 12:02             ` Xavier Bestel
2003-11-06 13:27             ` Scott Robert Ladd
2003-11-06 13:59               ` Richard B. Johnson
  -- strict thread matches above, loose matches on Subject: below --
2003-11-05 22:48 Chad Kitching
2003-11-05 22:53 ` Zwane Mwaikambo
2003-11-05 23:03 ` Larry McVoy
2003-11-06  0:52   ` Tomas Szepe
2003-11-06  1:57     ` Andreas Dilger
2003-11-06  2:20       ` Linus Torvalds
2003-11-06  3:01       ` Larry McVoy
2003-11-06 10:40         ` Matthias Andree
2003-11-06  4:09   ` Scott Robert Ladd
2003-11-06 10:06     ` bert hubert
2003-11-06 13:22       ` Theodore Ts'o
2003-11-06 14:43         ` Rik van Riel
2003-11-06 15:56       ` Linus Torvalds

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=20031106070721.GA18028@mcgroarty.net \
    --to=brian@mcgroarty.net \
    --cc=aebr@win.tue.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=zwane@arm.linux.org.uk \
    /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