{"vuid":"VU#107822","idnumber":"107822","name":"Symantec products vulnerable to buffer overflow via a specially crafted UPX file","keywords":["Symantec","buffer overflow","DEC2EXE","UPX file"],"overview":"The Symantec AntiVirus Library DEC2EXE component is vulnerable to remote arbitrary code execution.","clean_desc":"The Symantec AntiVirus Library is used in many Symantec and third-party virus scanning products, including Symantec Norton Antivirus and Symantec BrightMail AntiSpam. The AntiVirus Library DEC2EXE component contains a flaw in virtual file offset checking that can result in a heap overflow condition and the ability for an attacker to execute arbitrary code contained within the UPX file being scanned. Before the UPX file is uncompressed, the Portable Executable (PE) header is reconstructed. If a negative file offset to a crafted PE header is specified, and this crafted header contains malicious information, subsequent bounds calculations involving data from the legitimate PE header will result in a heap overflow.","impact":"A remote unauthenticated attacker is able to execute arbitrary code with no restrictions on content. This may not require manual intervention if the malicious file is sent to and automatically scanned by a client or server (such as an electronic mail gateway) that uses the Symantec AntiVirus Library.","resolution":"Apply an update\nUpdates for Symantec products are provided through the LiveUpdate functionality of the product or from the Symantec Product Support web page.","workarounds":"In the meantime, Symantec Security Response Bulletin SYM05-003 provides a number of workarounds to disable or remove the DEC2EXE module.","sysaffected":"","thanks":"Thanks to Alex Wheeler and the rest of the ISS X-Force for reporting this vulnerability.","author":"This document was written by Ken MacInnis and is based primarily on information provided by ISS X-Force and Symantec.","public":["http://www.sarc.com/avcenter/security/Content/2005.02.08.html","http://www.sarc.com/avcenter/venc/data/bloodhound.exploit.26.html","http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2005020911112648","http://xforce.iss.net/xforce/alerts/id/187","http://secunia.com/advisories/14179/","http://securitytracker.com/alerts/2005/Feb/1013133.html"],"cveids":["CVE-2005-0249"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2005-02-10T19:05:22Z","publicdate":"2005-02-08T00:00:00Z","datefirstpublished":"2005-02-10T22:26:31Z","dateupdated":"2005-02-22T20:20:25Z","revision":14,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"15","cam_exploitation":"0","cam_internetinfrastructure":"11","cam_population":"15","cam_impact":"18","cam_easeofexploitation":"9","cam_attackeraccessrequired":"17","cam_scorecurrent":"20.138625","cam_scorecurrentwidelyknown":"24.0114375","cam_scorecurrentwidelyknownexploited":"39.5026875","ipprotocol":"","cvss_accessvector":"","cvss_accesscomplexity":"","cvss_authentication":null,"cvss_confidentialityimpact":"","cvss_integrityimpact":"","cvss_availabilityimpact":"","cvss_exploitablity":null,"cvss_remediationlevel":"","cvss_reportconfidence":"","cvss_collateraldamagepotential":"","cvss_targetdistribution":"","cvss_securityrequirementscr":"","cvss_securityrequirementsir":"","cvss_securityrequirementsar":"","cvss_basescore":"","cvss_basevector":"","cvss_temporalscore":"","cvss_environmentalscore":"","cvss_environmentalvector":"","metric":20.138625,"vulnote":null}