{"vuid":"VU#880916","idnumber":"880916","name":"BitZipper 2013 memory-corruption vulnerability","keywords":["bitzipper","zip"],"overview":"BitZipper 2013 contains a memory-corruption vulnerability, which may allow a remote unauthenticated attacker to execute arbitrary code on a vulnerable system.","clean_desc":"BitZipper 2013 contains a memory-corruption vulnerability, which may allow a remote  unauthenticated attacker to execute arbitrary code on a vulnerable system.","impact":"By convincing a user to view a specially crafted ZIP document, an attacker may be able to execute arbitrary code on a vulnerable system.","resolution":"Update The vendor has stated that this vulnerability has been addressed in BitZipper 2013 Update 1. Users are advised to update to BitZipper 2013 Update 1 or later.","workarounds":"Use the Microsoft Enhanced Mitigation Experience Toolkit The Microsoft Enhanced Mitigation Experience Toolkit (EMET) can be used to help prevent exploitation of this vulnerability. CERT/CC has created a video tutorial for setting up EMET 3.0 on Windows 7. Note that platforms that do not support ASLR, such as Windows XP and Windows Server 2003, will not receive the same level of protection that modern Windows platforms will. Enable DEP in Microsoft Windows Consider enabling Data Execution Prevention (DEP) in supported versions of Windows. DEP should not be treated as a complete workaround, but it can mitigate the execution of attacker-supplied code in some cases. Microsoft has published detailed technical information about DEP in Security Research & Defense blog posts \"Understanding DEP as a mitigation technology\" part 1 and part 2. DEP should be used in conjunction with the application of patches or other mitigations described in this document. Note that when relying on DEP for exploit mitigation, it is important to use a system that supports Address Space Layout Randomization (ASLR) as well. ASLR is not supported by Windows XP or Windows Server 2003 or earlier. ASLR was introduced with Microsoft Windows Vista and Windows Server 2008. Please see the Microsoft SRD blog entry: On the effectiveness of DEP and ASLR for more details.","sysaffected":"","thanks":"Thanks to Christopher Gabriel of Telos Corporation \nfor reporting this vulnerability.","author":"This document was written by Michael Orlando.","public":["http://support.microsoft.com/kb/2458544","http://blogs.technet.com/srd/archive/2009/06/05/understanding-dep-as-a-mitigation-technology-part-1.aspx","http://blogs.technet.com/srd/archive/2009/06/12/understanding-dep-as-a-mitigation-technology-part-2.aspx","http://blogs.technet.com/b/srd/archive/2010/12/08/on-the-effectiveness-of-dep-and-aslr.aspx","http://www.bitzipper.com/"],"cveids":["CVE-2013-0138"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2013-02-25T19:33:51Z","publicdate":"2013-04-16T00:00:00Z","datefirstpublished":"2013-04-19T12:15:21Z","dateupdated":"2013-04-19T12:15:25Z","revision":11,"vrda_d1_directreport":"1","vrda_d1_population":"2","vrda_d1_impact":"3","cam_widelyknown":"0","cam_exploitation":"0","cam_internetinfrastructure":"0","cam_population":"0","cam_impact":"0","cam_easeofexploitation":"0","cam_attackeraccessrequired":"0","cam_scorecurrent":"0","cam_scorecurrentwidelyknown":"0","cam_scorecurrentwidelyknownexploited":"0","ipprotocol":"","cvss_accessvector":"L","cvss_accesscomplexity":"H","cvss_authentication":null,"cvss_confidentialityimpact":"N","cvss_integrityimpact":"N","cvss_availabilityimpact":"C","cvss_exploitablity":null,"cvss_remediationlevel":"W","cvss_reportconfidence":"UC","cvss_collateraldamagepotential":"L","cvss_targetdistribution":"L","cvss_securityrequirementscr":"ND","cvss_securityrequirementsir":"ND","cvss_securityrequirementsar":"ND","cvss_basescore":"4","cvss_basevector":"AV:L/AC:H/Au:N/C:N/I:N/A:C","cvss_temporalscore":"2.9","cvss_environmentalscore":"0.9","cvss_environmentalvector":"CDP:L/TD:L/CR:ND/IR:ND/AR:ND","metric":0.0,"vulnote":null}