[gs-bugs] [Bug 691532] jbig2dec segfault caused by new image reference counts

bugzilla-daemon at ghostscript.com bugzilla-daemon at ghostscript.com
Mon Aug 9 07:16:42 UTC 2010


--- Comment #4 from Ken Sharp <ken.sharp at artifex.com> 2010-08-09 07:16:42 UTC ---
(In reply to comment #3)
> xpdf and mupdf both crash on this as well.  Adobe (Acrobat 8) and Apple Preview
> each have wrong output.  I can't find a rip that prints this reasonably. 
> Anyway:
> The first segment header appears to be corrupt:
> 0x0, 0x0, 0x0, 0x1, 0x40, 0x0, 0x0, 0x33, 0x33, 0x33, 0x13, 0x0, 0x0, 0xa
> (section numbers from the draft spec cited at http://jbig2dec.sourceforge.net/)

It may not be relevant, but my anti-virus software detects this file as
infected with a trojan horse 'Dropper.Generic_c.AZV'. I wonder if the image is
deliberately corrupted in order to serve as an infection mechanism.

Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the gs-bugs mailing list