Sophos Antivirus CHM Chunk Name Length Memory Corruption Vulnerability iDefense Security Advisory 12.08.06 http://labs.idefense.com/intelligence/vulnerabilities/ Dec 08, 2006 I. BACKGROUND Sophos AntiVirus offers protection from the latest Trojans, worms and Viruses. More information is available on the vendors site at: http://sophos.com/products/ II. DESCRIPTION Sophos AntiVirus Engine is vulnerable to a Memory Corruption vulnerability when scanning malformed CHM archives. This memory corruption vulnerability can be triggered when Sophos Antivirus engine scans a malformed CHM file which has a large name length specified in a CHM chunk header. III. ANALYSIS Malformed CHM files can lead to a Memory Corruption condition on the local machine. This memory corruption vulnerability could potentially result in arbitrary code execution. Files received as email attachments, uploaded via web forms or otherwise saved to disk may trigger this condition if auto scanning is enabled on the target machine. Archive scanning is disabled by default and must be specified in order for this vulnerability to trigger. IV. DETECTION iDefense has confirmed this vulnerability in the following Sophos Antivirus products: * Sophos Small business edition (Linux) Product version: 4.06.1 Engine version : 2.34.3 Previous versions of Sophos Antivirus are suspected vulnerable. Other Sophos Antivirus products may also be vulnerable. Windows versions of the Sophos Antivirus product do not appear to be vulnerable. V. WORKAROUND Disabling the option to scan within archives will prevent exploitation of this vulnerability. VI. VENDOR RESPONSE Sophos has addressed this problem with new versions of their products. See http://www.sophos.com/support/knowledgebase/article/7609.html for more information. VII. CVE INFORMATION The Common Vulnerabilities and Exposures (CVE) project has assigned the name CVE-2006-5647 to this issue. This is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems. VIII. DISCLOSURE TIMELINE 09/28/2006 Initial vendor notification 10/02/2006 Initial vendor response 12/08/2006 Coordinated public disclosure IX. CREDIT This vulnerability was reported to iDefense by Damian Put <pucik@private>. Get paid for vulnerability research http://labs.idefense.com/methodology/vulnerability/vcp.php Free tools, research and upcoming events http://labs.idefense.com/ X. LEGAL NOTICES Copyright © 2006 iDefense, Inc. Permission is granted for the redistribution of this alert electronically. It may not be edited in any way without the express written consent of iDefense. If you wish to reprint the whole or any part of this alert in any other medium other than electronically, please e-mail customerservice@private for permission. Disclaimer: The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
This archive was generated by hypermail 2.1.3 : Tue Dec 12 2006 - 00:22:55 PST