All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: Michael Buesch <mbuesch@freenet.de>
Cc: Chris Wright <chrisw@osdl.org>,
	Chris White <webmaster@securesystem.info>,
	manuel@todo-linux.com, linux-kernel@vger.kernel.org
Subject: Re: Kernel fchown() exploit status?
Date: Fri, 9 Jul 2004 11:17:17 -0700	[thread overview]
Message-ID: <20040709111717.J1973@build.pdx.osdl.net> (raw)
In-Reply-To: <200407091146.32077.mbuesch@freenet.de>; from mbuesch@freenet.de on Fri, Jul 09, 2004 at 11:46:30AM +0200

* Michael Buesch (mbuesch@freenet.de) wrote:
> Is there an exploit available to test if the kernel has
> this vulnerability?

Just use of chown(2).

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

      parent reply	other threads:[~2004-07-09 18:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-08 21:06 Kernel fchown() exploit status? Chris White
2004-07-08 21:54 ` Manuel Arostegui Ramirez
2004-07-08 23:24 ` Chris Wright
2004-07-09  9:46   ` Michael Buesch
2004-07-09 10:02     ` Manuel Arostegui Ramirez
2004-07-09 18:17     ` Chris Wright [this message]

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=20040709111717.J1973@build.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manuel@todo-linux.com \
    --cc=mbuesch@freenet.de \
    --cc=webmaster@securesystem.info \
    /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 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.