+++ This bug was initially created as a clone of Bug #238420 +++
Description of problem:
There is a possible stack-based buffer overrun in function
plug-ins/common/sunras.c:set_color_table() that can be exploited by an
attacker to trigger execution of arbitrary code via crafted Sun RAS file.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Either use the program referred to in URL to generate a POC, or use one
that is attached to this bug.
Though I have reproduced a crash on all supported systems, as enumerated
above, for some unknown reason gdb was detaching from the plugin run with
GIMP_PLUGIN_DEBUG=sunras, so I was unable to do a depth-in investigation.
I deduce, that it is a stack overflow because core dumps showed evidence
of corrupt stack, with ssp glibc detects a stack smashing, and Secunia
advisory also states the same:
-- Additional comment from firstname.lastname@example.org on 2007-04-30 08:32 EST --
Created an attachment (id=153788)
Malformed Sun RAS file, that overflows stack in gimp's sunras plugin
fc5 -> devel
Upstream already has a fix by Sven Neumann, I've extracted that from the SVN
repo and built a fixed gimp-2.2.14-2.fc7 package. Pinged rel-eng to put it into
Found small packaging quirk that deleted symlinks to external plugins when
updated, gimp-2.2.14-3.fc7 should be fixed in that regard (which is building
right now). Pinged rel-eng.
BTW: Confirmed that the patch actually fixes the bug, i.e. doesn't crash the
plugin but gives a warning about "EOF encountered on reading".
Fixed the fix for the quirk mentioned in comment #3 in gimp-2.2.14-5.fc7.
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.
If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we're following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
Seems already fixed in Rawhide.