Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ismail Dönmez" <ismail@pardus.org.tr>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Do not crash reading UPX binaries
Date: Sun, 01 Jul 2007 22:12:00 -0000	[thread overview]
Message-ID: <200707020112.31603.ismail@pardus.org.tr> (raw)
In-Reply-To: <20070701215549.GA26528@caradoc.them.org>

[-- Attachment #1: Type: text/plain, Size: 755 bytes --]

On Monday 02 July 2007 00:55:49 Daniel Jacobowitz wrote:
> This patch issues an error instead of a segfault on the testcase
> in PR 2280.  UPX is a binary compression system; it's infamous for
> producing very strange files, which are only "just valid enough".
> In this case, it claims that the symbol table is at a large offset
> in a very small file.
>
> I don't think it's worth supporting files this modified.  Does anyone
> think we need to do better, or shall I check in the attached?

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

Regards,
ismail

-- 
Perfect is the enemy of good

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2007-07-01 22:12 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 [this message]
2007-07-01 22:28   ` Daniel Jacobowitz
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=200707020112.31603.ismail@pardus.org.tr \
    --to=ismail@pardus.org.tr \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.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