{"vuid":"VU#406236","idnumber":"406236","name":"Microsoft Publisher does not adequately validate Publisher documents","keywords":["Microsoft","Publisher","remote code execution","file","font","buffer overflow","stack","malformed string","ms06-sep"],"overview":"Microsoft Publisher does not adequately validate Publisher documents. This results in a buffer overflow vulnerability that could allow an attacker to execute arbitrary code with the privileges of the user running Publisher.","clean_desc":"Microsoft Publisher does not adequately validate strings within Publisher documents. Based on CT12-09-2006-2, the strings may be related to font information. The inadequate validation could allow a buffer overflow to occur. This vulnerability could be triggered when a user opens a specially crafted Publisher document.","impact":"By convincing a user to open a specially crafted Publisher document, a remote, unauthenticated attacker could execute arbitrary code with the privileges of the user running Publisher.","resolution":"Apply Updates Apply the appropriate updates (910729) referenced by Microsoft Security Bulletin MS06-054. Microsoft Knowledge Base Article 910729 describes known issues that may be caused by applying the updates. Specifically, updated versions of Publisher are no longer able to open Publisher 2.0 files.","workarounds":"Do not open untrusted documents Do not open unfamiliar or unexpected Publisher or other Office documents, particularly those hosted on web sites or delivered as email attachments. Please see Cyber Security Tip ST04-010 for more information. Do not rely on file name extension filtering In most cases, Windows will call Publisher to open a document even if the document has an unknown file extension. For example, if document.qwer contains the correct file header information, Windows will open document.qwer with Publisher. Filtering for common extensions (e.g., .pub, .doc, .dot, .rtf) may not detect all Publisher documents.","sysaffected":"","thanks":"This vulnerability was reported by Microsoft, who in turn credit Stuart Pearson of Computer Terrorism.","author":"This document was written by Art Manion.","public":["http://www.microsoft.com/technet/security/bulletin/ms06-054.mspx","http://support.microsoft.com/kb/924685","http://support.microsoft.com/kb/894540/","http://support.microsoft.com/kb/894541/","http://support.microsoft.com/kb/894542/","http://www.computerterrorism.com/research/ct12-09-2006-2.htm"],"cveids":["CVE-2006-0001"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2006-09-11T15:06:11Z","publicdate":"2006-09-12T00:00:00Z","datefirstpublished":"2006-09-12T20:42:33Z","dateupdated":"2006-09-15T19:59:05Z","revision":14,"vrda_d1_directreport":"0","vrda_d1_population":"3","vrda_d1_impact":"3","cam_widelyknown":"15","cam_exploitation":"0","cam_internetinfrastructure":"2","cam_population":"12","cam_impact":"16","cam_easeofexploitation":"10","cam_attackeraccessrequired":"12","cam_scorecurrent":"7.344","cam_scorecurrentwidelyknown":"9.504","cam_scorecurrentwidelyknownexploited":"18.144","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":7.344,"vulnote":null}