From: Manuel Arostegui Ramirez <manuel@todo-linux.com>
To: Michael Buesch <mbuesch@freenet.de>,
Chris Wright <chrisw@osdl.org>,
linux-kernel@vger.kernel.org
Cc: Chris White <webmaster@securesystem.info>
Subject: Re: Kernel fchown() exploit status?
Date: Fri, 9 Jul 2004 12:02:58 +0200 [thread overview]
Message-ID: <200407091202.58377.manuel@todo-linux.com> (raw)
In-Reply-To: <200407091146.32077.mbuesch@freenet.de>
El Viernes 09 Julio 2004 11:46, Michael Buesch escribió:
> -----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?
Look at this:
http://www.securityfocus.com/bid/10662/exploit/
It says that it's not exploit requiered to exploit this bug.
Any ideas, Chris White?
Cheers
--
Manuel Arostegui Ramirez #Linux Registered User 200896
next prev parent reply other threads:[~2004-07-09 10:04 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 [this message]
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=200407091202.58377.manuel@todo-linux.com \
--to=manuel@todo-linux.com \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--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.