Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 22 Nov 2014 21:15:21 +0100
From: Bastien ROUCARIES <>
Subject: Re: Stack smashing in libjpeg-turbo

On Thu, Nov 6, 2014 at 10:27 PM, Bastien ROUCARIES
<> wrote:
> Hi,
> Passing special crafted jpeg file to imagemagick (convert -rotate 270
> 003632r270.jpg junk.jpg) could lead to stack smashing in
> (libjpeg-turbo).
> This bug is triggered  by setting the optimize coding member of the
> JPEG initialization structure to TRUE. If this flag set it to FALSE,
> ImageMagick completes without complaint.
> Wokarround could consist to turn off compression optimization in
> imagemagick to prevent the stack smash.
> Please assing me CVE and make a cc to

We get a reduced test case that does not need imagemagick. The bug lie
in libjpeg-turbo. Upstream is investigating

> Bastien

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.