{"vuid":"VU#393305","idnumber":"393305","name":"Microsoft Office mailto URI remote code execution","keywords":["Microsoft","Office","Outlook","remote code execution","mailto URI","ms08-mar"],"overview":"A vulnerability in the way that Microsoft Outlook handles a certain type of hyperlink could allow a remote attacker to execute arbitrary code on the vulnerable system.","clean_desc":"Microsoft Outlook provides a centralized application for managing and organizing e-mail messages, schedules, tasks, notes, contacts, and other information. Outlook is included as a component of newer versions of Microsoft Office and available as a stand-alone product. Outlook exposes a vulnerability due to inadequate checking of parameters passed to the Outlook email client. The vulnerability is caused due to the manner in which Outlook interprest a mailto: URI. By creating a specially formatted mailto: URI, an attacker may be able to alter the way that Outlook is invoked in order to allow code execution. The malicious code could be delivered to the victim via a specially-crafted HTML email message or from a webpage controlled by the attacker.","impact":"Successful exploitation of this vulnerability could allow a remote, unauthenticated attacker to execute arbitrary code. Upon successful exploitation, the malicious code would be executed in the context of the \"Local Machine\" under the user running Outlook.","resolution":"Apply Update\nMicrosoft has addressed this vulnerability in Microsoft Security Bulletin MS08-015.","workarounds":"Workaround As stated directly from MS08-015: Disabling the mailto handler in the system registry key helps protect affected systems from attempts to exploit this vulnerability.","sysaffected":"","thanks":"Microsoft acknowledges Greg MacManus of \niDefense Labs\n for reporting this vulnerability.","author":"This document was written by Joseph W. Pruszynski.","public":["http://www.microsoft.com/technet/security/bulletin/ms08-015.mspx","http://blogs.technet.com/swi/archive/2008/03/11/protocol-handler-and-its-default-security-zone.aspx"],"cveids":["CVE-2008-0110"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2008-03-11T14:58:34Z","publicdate":"2008-03-11T00:00:00Z","datefirstpublished":"2008-03-11T20:52:10Z","dateupdated":"2008-04-01T19:34:31Z","revision":27,"vrda_d1_directreport":"0","vrda_d1_population":"3","vrda_d1_impact":"3","cam_widelyknown":"15","cam_exploitation":"2","cam_internetinfrastructure":"3","cam_population":"15","cam_impact":"18","cam_easeofexploitation":"13","cam_attackeraccessrequired":"20","cam_scorecurrent":"26.325","cam_scorecurrentwidelyknown":"32.90625","cam_scorecurrentwidelyknownexploited":"56.59875","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":26.325,"vulnote":null}