Red Hat Bugzilla – Bug 218932
CVE-2007-0010 GdbPixbufLoader fails to handle invalid input from Evolution correctly
Last modified: 2007-11-16 20:14:54 EST
+++ This bug was initially created as a clone of Bug #218755 +++
Description of problem:
evolution crashes on the spam mail I'll attach as mbox; the crash may well turn
out to be a security issue in itself. But just crashing is serious since the
next time evo opens it immediately goes back to the same mail and crashes again,
so a non-expert user cannot recover from this.
I suspect RHEL5 is affected too
-- Additional comment from firstname.lastname@example.org on 2006-12-07 06:07 EST --
Created an attachment (id=143043)
mbox with the crashing mail
-- Additional comment from email@example.com on 2006-12-08 10:08 EST --
The file "navigable.gif" is incorrectly encoded. I think evolution should not
feed underlying gdk with the corrupted data, but I doubt an assertion failure
there is the right way to handle the faulty gif.
When you extract the file (with reformime or evolution) and either try to view
it with firefox or gqview or embed it in another email message and open in
evolution it is correctly reported as being broken.
Moreover there's some interesting stuff in the broken base64 data: for example
the IN-SB-8XX-PLATFORMS string encoded there. How could it happen to came there?
Maybe this message was meant to exploit some windows software or encoded by a
horribly broken software? I got no smarter after disassembling the 8bit parts of
-- Additional comment from firstname.lastname@example.org on 2006-12-08 10:18 EST --
Created an attachment (id=143153)
Backtrace from FC6
Backported fix is in gtk2-2.4.13-20
Evolution in RHEL-3 doesn't crash, so the issue is virtually harmless there --
we won't issue an update for RHEL-3.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.