Patch at $URL
+*gimp-2.6.11-r5 (03 Sep 2011)
+ 03 Sep 2011; Sebastian Pipping <firstname.lastname@example.org> +gimp-2.6.11-r5.ebuild,
+ Integrate patch for security issue CVE-2011-2896 (bug #379289)
Do we need a dedicated bug for stabalizing 2.6.11-r5?
(In reply to comment #1)
> Do we need a dedicated bug for stabalizing 2.6.11-r5?
We usually stabilize in the same bug.
Arches, please test and mark stable:
target KEYWORDS : "alpha amd64 hppa ia64 ppc ppc64 sparc x86"
*** Bug 368967 has been marked as a duplicate of this bug. ***
+ 04 Sep 2011; Tony Vroon <email@example.com> gimp-2.6.11-r5.ebuild:
+ Marked stable on AMD64 based on arch testing by Elijah "Armageddon" El
+ Lazkani & Agostino "ago" Sarubbo in security bug #379289.
Stable for HPPA.
ppc/ppc64 stable, last arch done
Thanks, everyone. Added to existing GLSA request.
The LZW decompressor in the LWZReadByte function in giftoppm.c in the David
Koblas GIF decoder in PBMPLUS, as used in the gif_read_lzw function in
filter/image-gif.c in CUPS before 1.4.7, the LZWReadByte function in
plug-ins/common/file-gif-load.c in GIMP 2.6.11 and earlier, the LZWReadByte
function in img/gifread.c in XPCE in SWI-Prolog 5.10.4 and earlier, and
other products, does not properly handle code words that are absent from the
decompression table when encountered, which allows remote attackers to
trigger an infinite loop or a heap-based buffer overflow, and possibly
execute arbitrary code, via a crafted compressed stream, a related issue to
CVE-2006-1168 and CVE-2011-2895.
This issue was resolved and addressed in
GLSA 201209-23 at http://security.gentoo.org/glsa/glsa-201209-23.xml
by GLSA coordinator Sean Amoss (ackle).