From: Michael Shigorin <mike@osdn.org.ua>
To: community-en@altlinux.org
Subject: Re: [Comm-en] System call via buffer overflow not working
Date: Sat, 22 Jan 2005 01:33:05 +0200
Message-ID: <20050121233305.GP1188@osdn.org.ua> (raw)
In-Reply-To: <BAY24-F729214FA962434B69F7C2B3820@phx.gbl>
On Fri, Jan 21, 2005 at 05:32:42PM -0500, Aaron McDonald wrote:
> Linux Magazine has a buffer overflow article in the February
> 2005 issue. I enjoyed the article because I'd never read much
> about how to compromise a system using a buffer overflow
> strategy. I attempted to run two of the buffer overflow
> examples on my ALT Linux Sisyphus (20041129) box but found that
> the examples didn't work.
Ouch! :)
> I tried the examples on my Slackware 9.1 box (2.4 kernel) and
> everything worked!
Wonders.
> This second strategy involves storing a command in an
> environment variable and then passing this parameter to the
> system() function via a buffer overflow. In my case, the
> system() function is being called but it fails to execute the
> specified command.
I know that ALT's glibc has some hardening and sanitizing patches
-- you may want to grab src.rpm and examine them.
> I've included all the details below if anyone cares to look
> into this. I'm not dying to know the answer but it'd be cool to
> know what's going on here.
Not sure whether it's proper but if you're positively interested
it may be worth asking security@.
--
---- WBR, Michael Shigorin <mike@altlinux.ru>
------ Linux.Kiev http://www.linux.kiev.ua/
next prev parent reply other threads:[~2005-01-21 23:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-21 22:32 Aaron McDonald
2005-01-21 23:33 ` Michael Shigorin [this message]
2005-01-26 5:39 ` Aaron McDonald
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=20050121233305.GP1188@osdn.org.ua \
--to=mike@osdn.org.ua \
--cc=community-en@altlinux.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
ALT Linux users (in English only)
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/community-en/0 community-en/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 community-en community-en/ http://lore.altlinux.org/community-en \
community-en@lists.altlinux.org community-en@lists.altlinux.ru community-en@lists.altlinux.com
public-inbox-index community-en
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.community-en
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git