Nmap smb-vuln-cve2009-3103 NSE Script


This page contains detailed information about how to use the smb-vuln-cve2009-3103 NSE script. For list of all NSE scripts, visit the Nmap NSE Library.

Select:
Overview
Error Messages

Script Overview

Script source code: https://github.com/nmap/nmap/tree/master/scripts/smb-vuln-cve2009-3103.nse
Script categories: intrusive, exploit, dos, vuln
Target service / protocol: smb, netbios, tcp, udp
Target network port(s): 137, 139, 445
List of CVEs: CVE-2009-3103

Script Description

The smb-vuln-cve2009-3103.nse script detects Microsoft Windows systems vulnerable to denial of service (CVE-2009-3103). This script will crash the service if it is vulnerable.

The script performs a denial-of-service against the vulnerability disclosed in CVE-2009-3103. This works against Windows Vista and some versions of Windows 7, and causes a bluescreen if successful. The proof-of-concept code at http://seclists.org/fulldisclosure/2009/Sep/39 was used, with one small change.

This check was previously part of smb-check-vulns.

Smb-vuln-cve2009-3103 NSE Script Arguments

This is a full list of arguments supported by the smb-vuln-cve2009-3103.nse script:

smbdomain

The domain to log in with. If you aren't in a domain environment, then anything will (should?) be accepted by the server.

smbhash

A password hash to use when logging in. This is given as a single hex string (32 characters) or a pair of hex strings (both 32 characters, optionally separated by a single character). These hashes are the LanMan or NTLM hash of the user's password, and are stored on disk or in memory. They can be retrieved from memory using the fgdump or pwdump tools.

smbnoguest

Use to disable usage of the 'guest' account.

smbpassword

The password to connect with. Be cautious with this, since some servers will lock accounts if the incorrect password is given. Although it's rare that the Administrator account can be locked out, in the off chance that it can, you could get yourself in trouble. To use a blank password, leave this parameter off altogether.

smbtype

The type of SMB authentication to use. These are the possible options:

  • v1: Sends LMv1 and NTLMv1.
  • LMv1: Sends LMv1 only.
  • NTLMv1: Sends NTLMv1 only (default).
  • v2: Sends LMv2 and NTLMv2.
  • LMv2: Sends LMv2 only.
  • NTLMv2: Doesn't exist; the protocol doesn't support NTLMv2 alone. The default, NTLMv1, is a pretty decent compromise between security and compatibility. If you are paranoid, you might want to use v2 or lmv2 for this. (Actually, if you're paranoid, you should be avoiding this protocol altogether!). If you're using an extremely old system, you might need to set this to v1 or lm, which are less secure but more compatible. For information, see smbauth.lua.

smbusername

The SMB username to log in with. The forms "DOMAIN\username" and "username@DOMAIN" are not understood. To set a domain, use the smbdomain argument.

randomseed

Set to a value to change the filenames/service names that are randomly generated.

smbbasic

Forces the authentication to use basic security, as opposed to "extended security". Against most modern systems, extended security should work, but there may be cases where you want to force basic. There's a chance that you'll get better results for enumerating users if you turn on basic authentication.

smbport

Override the default port choice. If smbport is open, it's used. It's assumed to be the same protocol as port 445, not port 139. Since it probably isn't possible to change Windows' ports normally, this is mostly useful if you're bouncing through a relay or something.

smbsign

Controls whether or not server signatures are checked in SMB packets. By default, on Windows, server signatures aren't enabled or required. By default, this library will always sign packets if it knows how, and will check signatures if the server says to. Possible values are:

  • force: Always check server signatures, even if server says it doesn't support them (will Probably fail, but is technically more secure).
  • negotiate: [default] Use signatures if server supports them.
  • ignore: Never check server signatures. Not recommended.
  • disable: Don't send signatures, at all, and don't check the server's. not recommended. More information on signatures can be found in smbauth.lua.

vulns.short

If set, vulnerabilities will be output in short format, a single line consisting of the host's target name or IP, the state, and either the CVE ID or the title of the vulnerability. Does not affect XML output.

vulns.showall

If set, the library will show and report all the registered vulnerabilities which includes the NOT VULNERABLE ones. By default the library will only report the VULNERABLE entries: VULNERABLE, LIKELY VULNERABLE, VULNERABLE (DoS) and VULNERABLE (Exploitable). This argument affects the following functions: vulns.Report.make_output(): the default output function for portule/hostrule scripts. vulns.make_output(): the default output function for postrule scripts. vulns.format_vuln() and vulns.format_vuln_table() functions.

- - -
To use these script arguments, add them to the Nmap command line using the --script-args arg1=value,[arg2=value,..] syntax. For example:

nmap --script=smb-vuln-cve2009-3103 --script-args smbdomain=value,smbhash=value <target>

Smb-vuln-cve2009-3103 NSE Script Example Usage

Here's an example of how to use the smb-vuln-cve2009-3103.nse script:

nmap --script smb-vuln-cve2009-3103.nse -p445 <host>

nmap -sU --script smb-vuln-cve2009-3103.nse -p U:137,T:139 <host>

Smb-vuln-cve2009-3103 NSE Script Example Output

Here's a sample output from the smb-vuln-cve2009-3103.nse script:

Host script results:
| smb-vuln-cve2009-3103:
|   VULNERABLE:
|   SMBv2 exploit (CVE-2009-3103, Microsoft Security Advisory 975497)
|     State: VULNERABLE
|     IDs:  CVE:CVE-2009-3103
|           Array index error in the SMBv2 protocol implementation in srv2.sys in Microsoft Windows Vista Gold, SP1, and SP2,
|           Windows Server 2008 Gold and SP2, and Windows 7 RC allows remote attackers to execute arbitrary code or cause a
|           denial of service (system crash) via an & (ampersand) character in a Process ID High header field in a NEGOTIATE
|           PROTOCOL REQUEST packet, which triggers an attempted dereference of an out-of-bounds memory location,
|           aka "SMBv2 Negotiation Vulnerability." NOTE: some of these details are obtained from third party information.
|
|     Disclosure date: 2009-09-08
|     References:
|       http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3103
|_      https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-3103

Smb-vuln-cve2009-3103 NSE Script Example XML Output

There is no sample XML output for this module. However, by providing the -oX <file> option, Nmap will produce a XML output and save it in the file.xml file.

Authors

  • Ron Bowes
  • Jiayi Ye
  • Paulino Calderon <calderon()websec.mx>

References

See Also

Related NSE scripts to the smb-vuln-cve2009-3103.nse script:

Visit Nmap NSE Library for more scripts.

The smb-vuln-cve2009-3103.nse script may fail with the following error messages. Check for the possible causes by using the code snippets highlighted below found in the script source code. This can often times help in identifying the root cause of the problem.

Couldn't create socket

Here is a relevant code snippet related to the "Couldn't create socket" error message:

78:	    "\x4d\x20\x30\x2e\x31\x32\x00\x02\x53\x4d\x42\x20\x32\x2e" ..
79:	    "\x30\x30\x32\x00"
80:	
81:	  local socket = nmap.new_socket()
82:	  if(socket == nil) then
83:	    return false, "Couldn't create socket"
84:	  end
85:	
86:	  local status, result = socket:connect(host, 445)
87:	  if(status == false) then
88:	    socket:close()

Couldn't connect to host:

Here is a relevant code snippet related to the "Couldn't connect to host: " error message:

84:	  end
85:	
86:	  local status, result = socket:connect(host, 445)
87:	  if(status == false) then
88:	    socket:close()
89:	    return false, "Couldn't connect to host: " .. result
90:	  end
91:	
92:	  status, result = socket:send(buf)
93:	  if(status == false) then
94:	    socket:close()

Couldn't send the buffer:

Here is a relevant code snippet related to the "Couldn't send the buffer: " error message:

90:	  end
91:	
92:	  status, result = socket:send(buf)
93:	  if(status == false) then
94:	    socket:close()
95:	    return false, "Couldn't send the buffer: " .. result
96:	  end
97:	
98:	  -- Close the socket
99:	  socket:close()
100:

Couldn't create socket

Here is a relevant code snippet related to the "Couldn't create socket" error message:

103:	  stdnse.sleep(5)
104:	
105:	  -- Create a new socket
106:	  socket = nmap.new_socket()
107:	  if(socket == nil) then
108:	    return false, "Couldn't create socket"
109:	  end
110:	
111:	  -- Try and do something simple
112:	  stdnse.debug1("Attempting to connect to the host")
113:	  socket:set_timeout(5000)

Connect failed, host is likely vulnerable!

Here is a relevant code snippet related to the "Connect failed, host is likely vulnerable!" error message:

113:	  socket:set_timeout(5000)
114:	  status, result = socket:connect(host, 445)
115:	
116:	  -- Check the result
117:	  if(status == false or status == nil) then
118:	    stdnse.debug1("Connect failed, host is likely vulnerable!")
119:	    socket:close()
120:	    return true, VULNERABLE
121:	  end
122:	
123:	  -- Try sending something

Send failed, host is likely vulnerable!

Here is a relevant code snippet related to the "Send failed, host is likely vulnerable!" error message:

122:	
123:	  -- Try sending something
124:	  stdnse.debug1("Attempting to send data to the host")
125:	  status, result = socket:send("AAAA")
126:	  if(status == false or status == nil) then
127:	    stdnse.debug1("Send failed, host is likely vulnerable!")
128:	    socket:close()
129:	    return true, VULNERABLE
130:	  end
131:	
132:	  stdnse.debug1("Checks finished; host is likely not vulnerable.")

Version

This page has been created based on Nmap version 7.92.

Go back to menu.