From: Daniel Jacobowitz <drow@false.org>
To: "Ismail Dönmez" <ismail@pardus.org.tr>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Do not crash reading UPX binaries
Date: Sun, 01 Jul 2007 22:28:00 -0000 [thread overview]
Message-ID: <20070701222747.GA32509@caradoc.them.org> (raw)
In-Reply-To: <200707020112.31603.ismail@pardus.org.tr>
On Mon, Jul 02, 2007 at 01:12:27AM +0300, Ismail Dönmez wrote:
> Please not that attached gdbupx is from a security advisory [0] [1] but it
> looks like a simple DoS.
>
> [0] http://blog.xwings.net/?p=71
> [1] http://blogs.securiteam.com/index.php/archives/922
That would be useful in the report next time :-) I spent twenty
minutes figuring out what was going on, and yes, it was the invalid
symbol table pointer. I'm happy to hear that this won't affect all
UPX files after all, just truncated ones.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-07-01 22:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 21:56 Daniel Jacobowitz
2007-07-01 22:12 ` Ismail Dönmez
2007-07-01 22:28 ` Daniel Jacobowitz [this message]
2007-07-01 22:31 ` Ismail Dönmez
2007-07-02 1:53 ` Daniel Jacobowitz
2007-10-11 19:53 ` Daniel Jacobowitz
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=20070701222747.GA32509@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=ismail@pardus.org.tr \
/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