Nmap smb-vuln-ms06-025 NSE Script
This page contains detailed information about how to use the smb-vuln-ms06-025 NSE script. For list of all NSE scripts, visit the Nmap NSE Library.
Select: |
---|
Script Overview
Script source code: https://github.com/nmap/nmap/tree/master/scripts/smb-vuln-ms06-025.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-2006-2370
Script Description
The smb-vuln-ms06-025.nse script detects Microsoft Windows systems with Ras RPC service vulnerable to MS06-025.
MS06-025 targets the RasRpcSumbitRequest()
RPC method which is
a part of RASRPC interface that serves as a RPC service for configuring and
getting information from the Remote Access and Routing service. RASRPC can be
accessed using either "\ROUTER" SMB pipe or the "\SRVSVC" SMB pipe (usually on Windows XP machines).
This is in RPC world known as "ncan_np" RPC transport. RasRpcSumbitRequest()
method is a generic method which provides different functionalities according
to the RequestBuffer
structure and particularly the RegType
field within that
structure. RegType
field is of enum ReqTypes
type. This enum type lists all
the different available operation that can be performed using the RasRpcSubmitRequest()
RPC method. The one particular operation that this vuln targets is the REQTYPE_GETDEVCONFIG
request to get device information on the RRAS.
This script was previously part of smb-check-vulns.
Smb-vuln-ms06-025 NSE Script Arguments
This is a full list of arguments supported by the smb-vuln-ms06-025.nse script:
smbdomainThe domain to log in with. If you aren't in a domain environment, then anything will (should?) be accepted by the server.
smbhashA 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.
smbnoguestUse to disable usage of the 'guest' account.
smbpasswordThe 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.
smbtypeThe 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 usev2
orlmv2
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 tov1
orlm
, which are less secure but more compatible. For information, seesmbauth.lua
.
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.
Set to a value to change the filenames/service names that are randomly generated.
smbbasicForces 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.
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 insmbauth.lua
.
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-ms06-025 --script-args smbdomain=value,smbhash=value <target>
Smb-vuln-ms06-025 NSE Script Example Usage
Here's an example of how to use the smb-vuln-ms06-025.nse script:
nmap --script smb-vuln-ms06-025.nse -p445 <host>
nmap -sU --script smb-vuln-ms06-025.nse -p U:137,T:139 <host>
Smb-vuln-ms06-025 NSE Script Example Output
Here's a sample output from the smb-vuln-ms06-025.nse script:
| smb-vuln-ms06-025:
| VULNERABLE:
| RRAS Memory Corruption vulnerability (MS06-025)
| State: VULNERABLE
| IDs: CVE:CVE-2006-2370
| A buffer overflow vulnerability in the Routing and Remote Access service (RRAS) in Microsoft Windows 2000 SP4, XP SP1
| and SP2, and Server 2003 SP1 and earlier allows remote unauthenticated or authenticated attackers to
| execute arbitrary code via certain crafted "RPC related requests" aka the "RRAS Memory Corruption Vulnerability."
|
| Disclosure date: 2006-6-27
| References:
| https://technet.microsoft.com/en-us/library/security/ms06-025.aspx
|_ https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-2370
Smb-vuln-ms06-025 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
- https://nmap.org/nsedoc/scripts/smb-vuln-ms06-025.html
- https://github.com/nmap/nmap/tree/master/scripts/smb-vuln-ms06-025.nse
- https://technet.microsoft.com/en-us/library/security/ms06-025.aspx
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-2370
See Also
Related NSE scripts to the smb-vuln-ms06-025.nse script:
- smb2-capabilities.nse
- smb2-security-mode.nse
- smb2-time.nse
- smb2-vuln-uptime.nse
- smb-brute.nse
- smb-double-pulsar-backdoor.nse
- smb-enum-domains.nse
- smb-enum-groups.nse
- smb-enum-processes.nse
- smb-enum-services.nse
- smb-enum-sessions.nse
- smb-enum-shares.nse
- smb-enum-users.nse
- smb-flood.nse
- smb-ls.nse
- smb-mbenum.nse
- smb-os-discovery.nse
- smb-print-text.nse
- smb-protocols.nse
- smb-psexec.nse
- smb-security-mode.nse
- smb-server-stats.nse
- smb-system-info.nse
- smb-vuln-conficker.nse
- smb-vuln-cve2009-3103.nse
- smb-vuln-cve-2017-7494.nse
- smb-vuln-ms07-029.nse
- smb-vuln-ms08-067.nse
- smb-vuln-ms10-054.nse
- smb-vuln-ms10-061.nse
- smb-vuln-ms17-010.nse
- smb-vuln-regsvc-dos.nse
- smb-vuln-webexec.nse
- smb-webexec-exploit.nse
Visit Nmap NSE Library for more scripts.
The smb-vuln-ms06-025.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.
check_ms06_025: RRAS_SubmitRequest failed
Here is a relevant code snippet related to the "check_ms06_025: RRAS_SubmitRequest failed" error message:
106: rand.random_string(3000, "0123456789abcdefghijklmnoprstuvzxwyABCDEFGHIJKLMNOPRSTUVZXWY"))
107: status, sr_result = msrpc.RRAS_SubmitRequest(smbstate, req)
108: msrpc.stop_smb(smbstate)
109: --sanity check
110: if(status == false) then
111: stdnse.debug3("check_ms06_025: RRAS_SubmitRequest failed")
112: if(sr_result == "NT_STATUS_PIPE_BROKEN") then
113: return true, VULNERABLE
114: else
115: return true, PATCHED
116: end
Version
This page has been created based on Nmap version 7.92.
Go back to menu.