Bug 464041 (CVE-2008-4070) - CVE-2008-4070 Thunderbird cancelled newsgrop messages
Summary: CVE-2008-4070 Thunderbird cancelled newsgrop messages
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2008-4070
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL: http://nvd.nist.gov/nvd.cfm?cvename=C...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-26 01:00 UTC by Josh Bressers
Modified: 2019-09-29 12:26 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-04-19 22:03:33 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2008:0908 0 normal SHIPPED_LIVE Moderate: thunderbird security update 2008-10-01 15:35:17 UTC

Description Josh Bressers 2008-09-26 01:00:07 UTC 
From MFSA 2008-46:
Georgi Guninski reported a buffer overflow in the handling of cancelled
newsgroup messages. The error was caused by too small a heap buffer being
allocated to store message header information. This buffer could be overrun
by an attacker using a specially crafted message which could crash the mail
reader and potentially be used to run arbitrary code on the victim's
computer.
Comment 1 Fedora Update System 2008-11-21 10:55:50 UTC 
thunderbird-2.0.0.18-1.fc8 has been pushed to the Fedora 8 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 2 Fedora Update System 2008-11-21 11:03:36 UTC 
thunderbird-2.0.0.18-1.fc9 has been pushed to the Fedora 9 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 3 Vincent Danen 2010-04-19 22:03:33 UTC 
This vulnerability was resolved in Red Hat Enterprise Linux 4, 5, and Optional Productivity Applications version 5 via RHSA-2008:0908:

https://rhn.redhat.com/errata/RHSA-2008-0908.html
Note You need to log in before you can comment on or make changes to this bug.