Bug 218931 - CVE-2007-0010 GdbPixbufLoader fails to handle invalid input from Evolution correctly
Summary: CVE-2007-0010 GdbPixbufLoader fails to handle invalid input from Evolution co...
Keywords:
Status: CLOSED DUPLICATE of bug 219055
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: gtk2
Version: 5.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Matthew Barnes
QA Contact: Ben Levenson
URL:
Whiteboard: impact=moderate,source=vendor-sec,rep...
Depends On: 218755
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-12-08 15:39 UTC by Lubomir Kundrak
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-12-11 03:46:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lubomir Kundrak 2006-12-08 15:39:17 UTC
+++ 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 arjan.com on 2006-12-07 06:07 EST --
Created an attachment (id=143043)
mbox with the crashing mail


-- Additional comment from lkundrak 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
the part.

-- Additional comment from lkundrak on 2006-12-08 10:18 EST --
Created an attachment (id=143153)
Backtrace from FC6

evolution-2.8.2.1-2.fc6
gtk2-2.10.4-6.fc6

Comment 1 Matthias Clasen 2006-12-11 03:46:55 UTC

*** This bug has been marked as a duplicate of 219055 ***


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