{"vuid":"VU#112553","idnumber":"112553","name":"Apple QuickTime Player for Windows contains buffer overflow in processing of overly long QuickTime URLs","keywords":["Apple","QuickTime Player","buffer overflow","long string of characters","quicktime://","-u","URL"],"overview":"Apple's QuickTime Player is a player for files and streaming media in the QuickTime format. Versions of the player are available for both the Microsoft Windows and Apple MacOS platforms. A flaw in the version for Windows could allow a remote attacker to execute arbitrary code on a vulnerable system.","clean_desc":"A buffer overflow exists in the QuickTime Player for Windows' handling of overly long URL of the type quicktime://... A specially crafted URL consisting of a long string of characters can cause the QuickTime Player to crash or allow an attacker to execute arbitrary code of their choosing with the privileges of the user running the QuickTime Player. The URL containing the exploit code may be hosted on a webpage, introduced via HTML email, or presented to the user in another fashion that encourages them to browse to it.","impact":"If the QuickTime player software is instructed to load a URL that is specially crafted by an attacker, arbitrary code can be executed under the privileges of the QuickTime user. This crafted URL may be supplied on a webpage or in email for the victim to select, or some other means designed to encourage them to invoke the QuickTime Player using the exploit URL.","resolution":"Apply a patch from the vendor Apple has released a patch to address this vulnerability; please see the vendor section of this document for further details.","workarounds":"Removing the QuickTime handler from the web browser or removing the HKEY_CLASSES_ROOT/quicktime registry key may prevent automatic exploitation through HTML pages.","sysaffected":"","thanks":"This vulnerability was discovered by the staff at \nTexonet\n and reported by \niDEFENSE\n Labs.","author":"This document was written by Chad R Dougherty.","public":["h","t","t","p",":","/","/","w","w","w",".","i","d","e","f","e","n","s","e",".","c","o","m","/","a","d","v","i","s","o","r","y","/","0","3",".","3","1",".","0","3",".","t","x","t"],"cveids":["CVE-2003-0168"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2003-04-01T14:17:39Z","publicdate":"2003-03-31T00:00:00Z","datefirstpublished":"2003-04-01T20:06:14Z","dateupdated":"2003-04-01T20:06:21Z","revision":9,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"16","cam_exploitation":"0","cam_internetinfrastructure":"6","cam_population":"10","cam_impact":"19","cam_easeofexploitation":"10","cam_attackeraccessrequired":"20","cam_scorecurrent":"15.675","cam_scorecurrentwidelyknown":"18.525","cam_scorecurrentwidelyknownexploited":"32.775","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":15.675,"vulnote":null}