Nmap ajp-methods NSE Script

Script Overview

---

Script source code: https://github.com/nmap/nmap/tree/master/scripts/ajp-methods.nse
Script categories: default, safe
Target service / protocol: ajp13, tcp
Target network port(s): 8009
List of CVEs: -

Script Description

---

The ajp-methods.nse script discovers which options are supported by the AJP (Apache JServ Protocol) server by sending an OPTIONS request and lists potentially risky methods.

In this script, "potentially risky" methods are anything except GET, HEAD, POST, and OPTIONS. If the script reports potentially risky methods, they may not all be security risks, but you should check to make sure. This page lists the dangers of some common methods:

• http://www.owasp.org/index.php/Testing_for_HTTP_Methods_and_XST_%28OWASP-CM-008%29

Ajp-methods NSE Script Arguments

---

This is a full list of arguments supported by the ajp-methods.nse script:

ajp-methods.path

The path to check or / if none was given

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.

slaxml.debug

Debug level at which default callbacks will print detailed parsing info. Default: 3

http.host

The value to use in the Host header of all requests unless otherwise set. By default, the Host header uses the output of stdnse.get_hostname().

http.max-body-size

Limit the received body to specific number of bytes. An oversized body results in an error unless script argument http.truncated-ok or request option truncated_ok is set to true. The default is 2097152 (2MB). Use value -1 to disable the limit altogether. This argument can be overridden case-by-case with request option max_body_size.

http.max-cache-size

The maximum memory size (in bytes) of the cache.

http.max-pipeline

If set, it represents the number of outstanding HTTP requests that should be sent together in a single burst. Defaults to http.pipeline (if set), or to what function get_pipeline_limit returns.

http.pipeline

If set, it represents the number of HTTP requests that'll be sent on one connection. This can be set low to make debugging easier, or it can be set high to test how a server reacts (its chosen max is ignored).

http.truncated-ok

Do not treat oversized body as error. (Use response object flag truncated to check if the returned body has been truncated.) This argument can be overridden case-by-case with request option truncated_ok.

http.useragent

The value of the User-Agent header field sent with requests. By default it is "Mozilla/5.0 (compatible; Nmap Scripting Engine; https://nmap.org/book/nse.html)". A value of the empty string disables sending the User-Agent header field.

- - -
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=ajp-methods --script-args ajp-methods.path=value,smbdomain=value <target>

Ajp-methods NSE Script Example Usage

---

Here's an example of how to use the ajp-methods.nse script:

nmap -p 8009 <ip> --script ajp-methods

Ajp-methods NSE Script Example Output

---

Here's a sample output from the ajp-methods.nse script:

PORT     STATE SERVICE
8009/tcp open  ajp13
| ajp-methods:
|   Supported methods: GET HEAD POST PUT DELETE TRACE OPTIONS
|   Potentially risky methods: PUT DELETE TRACE
|_  See https://nmap.org/nsedoc/scripts/ajp-methods.html

Ajp-methods 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.

Author

---

• Patrik Karlsson

References

---

• https://nmap.org/nsedoc/scripts/ajp-methods.html
• https://github.com/nmap/nmap/tree/master/scripts/ajp-methods.nse
• http://www.owasp.org/index.php/Testing_for_HTTP_Methods_and_XST_%28OWASP-CM-008%29

See Also

---

Related NSE scripts to the ajp-methods.nse script:

• ajp-auth.nse
• ajp-brute.nse
• ajp-headers.nse
• ajp-request.nse

Visit Nmap NSE Library for more scripts.

The ajp-methods.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.

Failed to connect to server

---

Here is a relevant code snippet related to the "Failed to connect to server" error message:

55:	
56:	action = function(host, port)
57:	
58:	  local helper = ajp.Helper:new(host, port)
59:	  if ( not(helper:connect()) ) then
60:	    return stdnse.format_output(false, "Failed to connect to server")
61:	  end
62:	
63:	  local status, response = helper:options(arg_url)
64:	  helper:close()
65:	  if ( not(status) or response.status ~= 200 or

Failed to get a valid response for the OPTION request

---

Here is a relevant code snippet related to the "Failed to get a valid response for the OPTION request" error message:

62:	
63:	  local status, response = helper:options(arg_url)
64:	  helper:close()
65:	  if ( not(status) or response.status ~= 200 or
66:	    not(response.headers) or not(response.headers['allow']) ) then
67:	    return "Failed to get a valid response for the OPTION request"
68:	  end
69:	
70:	  local methods = stringaux.strsplit(",%s", response.headers['allow'])
71:	
72:	  local output = {}