{"vuid":"VU#124113","idnumber":"124113","name":"Microsoft Exchange Outlook Web Access UTF character set label script injection vulnerability","keywords":["Microsoft","Exchange","Outlook Web Access","information disclosure","script-based attachments","ms07-may","xss"],"overview":"Microsoft Exchange Outlook Web Access (OWA) fails to properly handle the UTF character set label, which can allow a remote, unauthenticated attacker to execute script within the security context of the OWA user.","clean_desc":"OWA allows users to access their email accounts on a Microsoft Exchange server from another host through a web browser. When a user opens a script-based email attachment, the web browser may execute the script on the client side. If executed, the script would have all the privileges of the OWA user, including access to and manipulation of messages and folders on the server.","impact":"A remote attacker with the ability to supply an email message containing specially crafted script may be able to execute the script in the security context of the victim user on the client system. For more information about this type of vulnerability, please see CERT Advisory CA-2000-02.","resolution":"Apply an update\nThis issue is addressed in Microsoft Security Bulletin MS07-026.","workarounds":"Workarounds Microsoft Security Bulletin MS07-026 provides several workarounds, including disabling OWA and restricting HTML attachments.","sysaffected":"","thanks":"This vulnerability was reported by Microsoft, who in turn credit Martijn Brinkers of Izecom.","author":"This document was written by Will Dormann.","public":["http://www.microsoft.com/technet/security/bulletin/ms07-026.mspx","Improper authorization checking in IOS FTP server"],"cveids":["CVE-2007-0220"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2007-05-08T18:05:37Z","publicdate":"2007-05-08T00:00:00Z","datefirstpublished":"2007-05-08T19:58:36Z","dateupdated":"2007-05-09T17:35:17Z","revision":6,"vrda_d1_directreport":"0","vrda_d1_population":"4","vrda_d1_impact":"4","cam_widelyknown":"16","cam_exploitation":"0","cam_internetinfrastructure":"10","cam_population":"14","cam_impact":"4","cam_easeofexploitation":"10","cam_attackeraccessrequired":"20","cam_scorecurrent":"5.46","cam_scorecurrentwidelyknown":"6.3","cam_scorecurrentwidelyknownexploited":"10.5","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":5.46,"vulnote":null}