{"vuid":"VU#26493","idnumber":"26493","name":"MS Excel XLM Text Macro execution fails to trigger warning when default medium security set","keywords":["MS Excel","XLM","Excel 4.0 Macro Language","text","macro","Macros","MS00-022"],"overview":"Excel fails to present a warning dialog when a macro is called from an external XLM (text macro) file.","clean_desc":"If a spreadsheet contains a reference to an external macro (XLM) file, Excel does not generate the usual warning dialog asking if the user wants to run the macro. Microsoft reports that the macros can not be automatically executed, and that the user must trigger the macro. It is possible that actions such as changing the cell focus are sufficient to trigger a macro however. The file types that may include a reference to an external macro include: comma separated values, tab delimited text, and data interchange format. Excel 97 and Excel 2000 have this vulnerability. Microsoft has published a security bulletin with additional information at: http://www.microsoft.com/technet/security/bulletin/MS00-022.asp","impact":"Users may be tricked into executing an Excel macro, allowing the creator of the spreadsheet to execute arbitrary commands as the user opening the spreadsheet.","resolution":"Apply a Patch Microsoft has produced patches to correct this vulnerability. The patches are referenced in their advisory at: http://www.microsoft.com/technet/security/bulletin/MS00-022.asp","workarounds":"Set Macro Security Level to\"High\" Setting the macro execution security level to \"High\", will prevent the macros from running.","sysaffected":"","thanks":"Microsoft credits Darryl Higa for finding this vulnerability.","author":"This document was written by Cory F. Cohen.","public":["http://www.microsoft.com/technet/security/bulletin/MS00-022.asp","http://www.microsoft.com/technet/security/bulletin/MS00-022.asp?a=printable","http://www.microsoft.com/technet/security/bulletin/fq00-022.asp","http://www.microsoft.com/technet/support/kb.asp?ID=255605","http://www.microsoft.com/technet/support/kb.asp?ID=255606","http://www.officeupdate.com/2000/downloadDetails/O2kSR1DDL.htm","http://www.officeupdate.com/downloadDetails/Xl8p9pkg.htm?s=/downloadCatalog/dldExcel.asp"],"cveids":["CVE-2000-0277"],"certadvisory":"","uscerttechnicalalert":null,"datecreated":"2000-04-05T21:13:01Z","publicdate":"2000-04-03T00:00:00Z","datefirstpublished":"2002-09-27T17:39:03Z","dateupdated":"2002-09-27T17:39:22Z","revision":5,"vrda_d1_directreport":"","vrda_d1_population":"","vrda_d1_impact":"","cam_widelyknown":"20","cam_exploitation":"0","cam_internetinfrastructure":"5","cam_population":"19","cam_impact":"15","cam_easeofexploitation":"2","cam_attackeraccessrequired":"15","cam_scorecurrent":"4.0078125","cam_scorecurrentwidelyknown":"4.0078125","cam_scorecurrentwidelyknownexploited":"7.2140625","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":4.0078125,"vulnote":null}