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

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoting Chris Wright <chrisw@osdl.org>:
> * Chris White (webmaster@securesystem.info) wrote:
> > There was a recent security announcment regarding a vulnerability with 
> > the fchown function.
> > 
> > Only a few distrobutions (red hat/suse) have fixed the issue, but I've 
> > yet to see a general patch for it.
> 
> Patches are in both 2.4 and 2.6 bk trees.  2.4.27-rc3 has this fixed.
> There hasn't been a 2.6.8-rc release since the patches went in to 2.6

Is there an exploit available to test if the kernel has
this vulnerability?

- -- 
Regards Michael Buesch  [ http://www.tuxsoft.de.vu ]


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA7ml2FGK1OIvVOP4RAtU7AKCX9p7P389fBEfb1uY0q0VEgKYYfACgjY3x
X4nZPpoLbFJVpRwQOtKCbOk=
=E2bp
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-07-09  9:48 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 [this message]
2004-07-09 10:02     ` Manuel Arostegui Ramirez
2004-07-09 18:17     ` Chris Wright

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=200407091146.32077.mbuesch@freenet.de \
    --to=mbuesch@freenet.de \
    --cc=chrisw@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.