Bug 217560 (CVE-2006-5868) - CVE-2006-5868 Insufficient boundary check in ImageMagick's SGIDecode()
Summary: CVE-2006-5868 Insufficient boundary check in ImageMagick's SGIDecode()
Alias: CVE-2006-5868
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Norm Murray
QA Contact:
URL: http://www.debian.org/security/2006/d...
Depends On: 217558
TreeView+ depends on / blocked
Reported: 2006-11-28 17:00 UTC by Lubomir Kundrak
Modified: 2021-11-12 19:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-04-26 07:43:46 UTC

Attachments (Terms of Use)

Description Lubomir Kundrak 2006-11-28 17:00:19 UTC
+++ This bug was initially created as a clone of Bug #217558 +++

Description of problem:

Debian team issued an ImageMagick update DSA-1213-1 where they reportedly fixed
an issue in SGI image handling routine.

See their Changelog entry:
  * Fix insufficient boundary checks in SGIDecode() (discovered by Daniel
And excerpt from their advisory:
    Daniel Kobras discovered that Imagemagick is vulnerable to buffer
    overflows in the module for SGI images.

Version-Release number of selected component (if applicable):


Additional info:

I attach relevant part of the debian patch. Please have a look at it.

-- Additional comment from lkundrak on 2006-11-28 11:57 EST --
Created an attachment (id=142305)
Part that fixes CVE-2006-5868 issue, from debian

Comment 1 Lubomir Kundrak 2006-12-21 20:05:54 UTC
Upstream's revision 4399 (which went into 6.2.9) changes SGIDecode quite
radically, possibly to address the issue. I wish they learned to write commit
messages. I mailed the upstream to get some more clue...

Comment 2 Lubomir Kundrak 2006-12-22 10:29:26 UTC
Upstream states that the flaw was corrected in

Comment 3 Lubomir Kundrak 2007-11-02 17:40:00 UTC
Please close if ImageMagick- fixes this, otherwise push the fix. I
think rebasing would be the best thing to do here.

Comment 4 Bug Zapper 2008-04-04 04:59:44 UTC
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers

Comment 5 Hans de Goede 2008-04-26 07:43:46 UTC
Short intro: I'm a new co-maintainer of ImageMagick and as such walking through
all open bugs.

This bug is fixed in F-7 and newerm closing.

Note You need to log in before you can comment on or make changes to this bug.