Metamail email message boundary header buffer overflow
| metamail-boundary-bo (24702) |  High Risk |
Description:
Metamail is vulnerable to a buffer overflow caused by improper bounds checking of boundary headers. By creating a malicious email message containing an overly long boundary header, a remote attacker could overflow a buffer and cause the application to crash or possibly execute arbitrary code on the victim's system, once the malicious email is processed by Metamail.
*CVSS:
| Base Score: | 5.6 |
| Access Vector: | Remote |
| Access Complexity: | High |
| Authentication: | Not Required |
| Confidentiality Impact: | Partial |
| Integrity Impact: | Partial |
| Availability Impact: | Partial |
| Temporal Score: | 4.1 |
| Exploitability: | Unproven |
| Remediation Level: | Official-Fix |
| Report Confidence: | Confirmed |
Consequences:
Gain Access
Remedy:
For Debian GNU/Linux:
Refer to DSA-996-1 for patch, upgrade, or suggested workaround information. See References.
For Red Hat Linux:
Refer to RHSA-2006:0217-4 for patch, upgrade, or suggested workaround information. See References.
For Gentoo Linux:
Refer to Gentoo Linux Security Announcement GLSA 2006-03-16 for patch, upgrade, or suggested workaround information. See References.
For other distributions:
Contact your vendor for upgrade or patch information.
References:
- Debian Bug report logs - #352482: metamail: crashes with very long boundaries in messages.
- ASA-2006-060: metamail security update (RHSA-2006-0217)
- BID-16611: Metamail Message Processing Remote Buffer Overflow Vulnerability
- CVE-2006-0709: Buffer overflow in Metamail 2.7-50 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via e-mail messages with a long boundary attribute, a different vulnerability than CVE-2004-0105.
- DSA-995: metamail -- buffer overflow
- GLSA-200603-16: Metamail: Buffer overflow
- MDKSA-2006:047: Updated metamail packages fix vulnerability
- RHSA-2006-0217: metamail security update
- SA18796: Metamail Mail Boundary Handling Buffer Overflow
- SECTRACK ID: 1015654: Metamail Buffer Overflow Lets Remote Users Deny Service
- SUSE-SR:2006:005: SUSE Security Summary Report
- VUPEN/ADV-2006-0565: Metamail Mail Boundary Handling Remote Buffer Overflow Vulnerability
Platforms Affected:
- Debian Debian Linux 3.0
- Debian Debian Linux 3.1
- Gentoo Linux
- MandrakeSoft Mandrake Linux 10.1 X86_64
- MandrakeSoft Mandrake Linux 10.1
- MandrakeSoft Mandrake Linux 2006 X86_64
- MandrakeSoft Mandrake Linux 2006
- MandrakeSoft Mandrake Linux LE2005
- MandrakeSoft Mandrake Linux LE2005 X86_64
- MandrakeSoft Mandrake Linux Corporate Server 3.0 X86_64
- MandrakeSoft Mandrake Linux Corporate Server 3.0
- RedHat Enterprise Linux 2.1 ES
- RedHat Enterprise Linux 2.1 AS
- RedHat Enterprise Linux 2.1 WS
- RedHat Linux Advanced Workstation 2.1 Itanium
- Telcordia Technologies Metamail 2.7
Reported:
Feb 14, 2006
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net
* According to the Forum of Incident Response and Security Teams (FIRST), the Common Vulnerability Scoring System (CVSS) is an "industry open standard designed to convey vulnerability severity and help to determine urgency and priority of response." IBM PROVIDES THE CVSS SCORES "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. CUSTOMERS ARE RESPONSIBLE FOR ASSESSING THE IMPACT OF ANY ACTUAL OR POTENTIAL SECURITY VULNERABILITY.
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall IBM be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.