From: Lethalman <lethalman@fyrebird.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Fix for new elf_loader bug?
Date: Sat, 08 Jan 2005 14:46:47 +0100 [thread overview]
Message-ID: <41DFE447.9030402@fyrebird.net> (raw)
In-Reply-To: <41DFD9CC.9080009@fyrebird.net>
Frank Steiner wrote:
> Hi,
>
> is there already a patch for the new problem with the elf loader, maybe
> in the bitkeeper tree?
>
> http://www.isec.pl/vulnerabilities/isec-0021-uselib.txt
>
> Thanks!
> cu,
> Frank
I made this very very very very very simple patch for kernel 2.4.28:
http://maphia.flowsecurity.org/patch/uselib-2.4.28.patch
The only thing that an attacker can do is to repeat the exploit and
cause a DoS, but it's hard too.
--
www.iosn.it * Amministratore Italian Open Source Network
www.fyrebird.net * Fyrebird Hosting Provider - Technical Department
prev parent reply other threads:[~2005-01-08 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-07 15:49 Fix for new elf_loader bug? Frank Steiner
2005-01-07 17:05 ` Marcelo Tosatti
2005-01-07 22:26 ` Vasil Kolev
2005-01-07 20:06 ` Marcelo Tosatti
2005-01-07 22:49 ` Chris Wright
[not found] ` <41DFD9CC.9080009@fyrebird.net>
2005-01-08 13:46 ` Lethalman [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=41DFE447.9030402@fyrebird.net \
--to=lethalman@fyrebird.net \
--cc=linux-kernel@vger.kernel.org \
/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