Bug 218931 - CVE-2007-0010 GdbPixbufLoader fails to handle invalid input from Evolution correctly
CVE-2007-0010 GdbPixbufLoader fails to handle invalid input from Evolution co...
Status: CLOSED DUPLICATE of bug 219055
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: gtk2 (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Matthew Barnes
Ben Levenson
: Security
Depends On: 218755
  Show dependency treegraph
Reported: 2006-12-08 10:39 EST by Lubomir Kundrak
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-12-10 22:46:55 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

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

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

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

Comment 1 Matthias Clasen 2006-12-10 22:46:55 EST

*** 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.