{"vuid":"VU#599832","idnumber":"599832","name":"Microsoft Internet Explorer Script Error Handling Memory Corruption Vulnerability","keywords":["Microsoft","Internet Explorer","Script Error Handling","Memory Corruption","ms06-dec"],"overview":"A vulnerability in the way Microsoft Internet Explorer handles certain script errors may lead to memory corruption that may allow remote execution of arbitrary code.","clean_desc":"Microsoft Internet Explorer contains a memory corruption vulnerability that could be exploited when handling script errors. According to Microsoft Security Bulletin MS06-072: Internet Explorer attempts to access previously freed memory when handling script errors in certain situations.","impact":"A remote, unauthenticated attacker may be able to execute arbitrary code or cause a denial-of-service condition.","resolution":"Update\nMicrosoft has released an update to address this issue. See Microsoft Security Bulletin MS06-072 for more details.","workarounds":"Disable scripting Disable scripting as specified in the Securing Your Web Browser document and the Malicious Web Scripts FAQ. Do not follow unsolicited links In order to convince users to visit their sites, attackers often use URL encoding, IP address variations, long URLs, intentional misspellings, and other techniques to create misleading links. Do not click on unsolicited links received in email, instant messages, web forums, or internet relay chat (IRC) channels. Type URLs directly into the browser to avoid these misleading links. While these are generally good security practices, following these behaviors will not prevent exploitation of this vulnerability in all cases, particularly if a trusted site has been compromised or allows cross-site scripting.","sysaffected":"","thanks":"This vulnerability was reported in Microsoft Security Bulletin \nMS06-072\n. Microsoft credits Jakob Balle and Carsten Eiram of Secunia Research for reporting this issue.","author":"This document was written by Chris Taschner.","public":["h","t","t","p",":","/","/","w","w","w",".","m","i","c","r","o","s","o","f","t",".","c","o","m","/","t","e","c","h","n","e","t","/","s","e","c","u","r","i","t","y","/","b","u","l","l","e","t","i","n","/","m","s","0","6","-","0","7","2",".","m","s","p","x"],"cveids":["CVE-2006-5579"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2006-12-12T19:03:12Z","publicdate":"2006-12-12T00:00:00Z","datefirstpublished":"2006-12-13T13:14:18Z","dateupdated":"2006-12-18T18:31:49Z","revision":10,"vrda_d1_directreport":"0","vrda_d1_population":"4","vrda_d1_impact":"4","cam_widelyknown":"15","cam_exploitation":"0","cam_internetinfrastructure":"3","cam_population":"15","cam_impact":"20","cam_easeofexploitation":"12","cam_attackeraccessrequired":"20","cam_scorecurrent":"24.3","cam_scorecurrentwidelyknown":"31.05","cam_scorecurrentwidelyknownexploited":"58.05","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":24.3,"vulnote":null}