| VID |
26054 |
| Severity |
40 |
| Port |
139,445 |
| Protocol |
TCP |
| Class |
SMB |
| Detailed Description |
The hotfix (KB823980) for the 'Buffer Overflow Vulnerability in RPC Interface' has not been applied.
Remote Procedure Call (RPC) is a protocol used by the Windows operating system, which provides an inter-process communication mechanism that allows a program running on one computer to seamlessly execute code on a remote system. However, there is a buffer overflow vulnerability that can be exploited remotely via a DCOM RPC interface that listens on TCP/UDP port 135. The vulnerability results because the Windows RPC service does not properly check message inputs under certain circumstances. To exploit this vulnerability, a remote attacker will send a specially formed request to the remote computer on specific RPC ports. It results that a remote attacker can overflow a buffer and gain complete control over a remote computer, which allows them to take any action on the server that they want, such as changing Web pages, reformatting the hard disk, or adding new users to the local administrators group.
This vulnerability may be exposed on other ports that the RPC Endpoint Mapper listens on, such as TCP ports 139, 135, 445 and 593.
* Note: This check requires an account with Guest or upper privileges which can access the registry of the remote host to scan. Absence of these condition will result in the check not being performed and a False Negative for all vulnerable hosts.
* References:
http://www.microsoft.com/technet/security/bulletin/ms03-026.asp
* Platforms Affected:
Windows NT 4.0 Server, SP 6a
Windows NT 4.0 Terminal Server Edition, SP 6
Windows 2000, SP3, SP4
Windows XP 32 bit Edition, SP1
Windows XP 64 bit Edition, SP1
Windows Server 2003 32 bit Edition
Windows Server 2003 64 bit Edition |
| Recommendation |
Apply the appropriate patch for your system, as listed in Microsoft's security bulletin MS03-026 at http://www.microsoft.com/technet/security/bulletin/ms03-026.asp
-- OR --
Patches for Windows platforms are also available from the Microsoft Windows Update Web site, http://windowsupdate.microsoft.com . Windows Update detects what version of Windows you are running and offers the appropriate patch.
Workarounds:
Block the port 135(139,445,593) at your firewall.
For Windows XP or Windows Server 2003, you can use the Internet Connection Firewall to block inbound RPC traffic from the Internet by default.
-- OR --
Disable DCOM on all affected machines.
1. Run Dcomcnfg.exe via Run from Start menu.
For Windows XP or Windows Server 2003, perform these additional steps:
1) Click on the Component Services node under Console Root and Open the Computers sub-folder.
2) For the local computer, right click on My Computer and choose Properties.
3) For a remote computer, right click on the Computers folder and choose New then Computer.
Enter the computer name. Right click on that computer name and choose Properties.
2. Choose the <Default Properties> tab.
3. Select (or clear) the "Enable Distributed COM on this Computer" check box.
If service is disabled, all communication between objects on that computer and objects on other computers will be disabled. If you disable DCOM on a remote computer, you will not be able to remotely access that computer afterwards to re-enable DCOM. To re-enable DCOM, you will need physical access to that computer. |
| Related URL |
CVE-2003-0352 (CVE) |
| Related URL |
8205 (SecurityFocus) |
| Related URL |
12629 (ISS) |
|
