Bug 181665 - CVE-2006-0709 Metamail heap based buffer overflow
Summary: CVE-2006-0709 Metamail heap based buffer overflow
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: metamail
Version: 2.1
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Nalin Dahyabhai
QA Contact:
URL:
Whiteboard: source=debian,reported=20060213,publi...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-15 19:25 UTC by Josh Bressers
Modified: 2007-11-30 22:06 UTC (History)
1 user (show)

Fixed In Version: RHSA-2006-0217
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 14:32:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Reproducer that crashes on RHEL2.1 (15.49 KB, text/plain)
2006-02-15 21:22 UTC, Josh Bressers
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2006:0217 0 normal SHIPPED_LIVE Important: metamail security update 2006-02-21 05:00:00 UTC

Description Josh Bressers 2006-02-15 19:25:05 UTC
Metamail heap based buffer overflow

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=352482

A bug was found in the way metmail processes boundaries in mail
messages.  This issue is a pretty standard heap based buffer overflow.
The Debian bug has a reproducer and a patch.

This issue has been rated as Important since the elm mail reader uses
metamail to handle MIME messages.

Comment 2 Josh Bressers 2006-02-15 21:22:40 UTC
Created attachment 124705 [details]
Reproducer that crashes on RHEL2.1

Comment 5 Red Hat Bugzilla 2006-02-21 14:33:00 UTC
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.

http://rhn.redhat.com/errata/RHSA-2006-0217.html



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