Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 22 Nov 2010 11:32:38 -0500 (EST)
From: "Steven M. Christey" <>
Subject: Re: CVE Request: gif2png: command-line buffer overflow

This type of error may happen when executing from a shell, but not 
necessarily *every* shell, and not when shell execution is bypassed e.g. 
when using exec()... so the vulnerable program might still execute.

- Steve

On Mon, 22 Nov 2010, Benji wrote:

> "File name too long"
> ------Original Message------
> From: Dan Rosenberg
> To:
> ReplyTo:
> Subject: Re: [oss-security] CVE Request: gif2png: command-line buffer overflow problem
> Sent: Nov 22, 2010 00:19
> How could this possibly be exploited?  If you can trick a user into
> running gif2png [exploit payload], then that user has already lost.
> See also:
> make `perl -e 'print "A"x10000'`
> -Dan
> On Sun, Nov 21, 2010 at 6:45 PM, Kurt Seifried <> wrote:
>> This is from 2009 but doesn't appear to have a CVE (no "gif2png" in
>> the CVE database).
>> Sources:
>> Description:
>> A buffer overflow in gif2png 2.5.3 and earlier allows an attacker to
>> execute arbitrary code via a long command line argument passed to the
>> gif2png binary.
>> It was first claimed that it was fixed in 2.5.2 but it is reported
>> that it isn't fixed, I tested 2.5.3 and it still seg faults the same
>> way as 2.5.2 so it would appear it was never fixed, as the software
>> was last updated in 2005 I guess this one never gets fixed.
>> --
>> Kurt Seifried
>> tel: 1-703-879-3176
> Sent from my BlackBerry® wireless device

Powered by blists - more mailing lists

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.