Nmap ajp-request NSE Script


This page contains detailed information about how to use the ajp-request 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/ajp-request.nse
Script categories: discovery, safe
Target service / protocol: ajp13, tcp
Target network port(s): 8009
List of CVEs: -

Script Description

The ajp-request.nse script requests a URI over the Apache JServ Protocol and displays the result (or stores it in a file). Different AJP methods such as; GET, HEAD, TRACE, PUT or DELETE may be used.

The Apache JServ Protocol is commonly used by web servers to communicate with back-end Java application server containers.

Ajp-request NSE Script Arguments

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

filename

The name of the file where the results should be stored

method

AJP method to be used when requesting the URI (default: GET)

password

The password to use to access protected resources

path

The path part of the URI to request

username

The username to use to access protected resources

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-request --script-args filename=value,method=value <target>

Ajp-request NSE Script Example Usage

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

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

Ajp-request NSE Script Example Output

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

PORT     STATE SERVICE
8009/tcp open  ajp13
| ajp-request:
| <!DOCTYPE HTML>
| <html>
| <head>
| <title>JSP Test</title>
|
| </head>
| <body>
| <h2>Hello, World.</h2>
| Fri May 04 02:09:40 UTC 2012
| </body>
|_</html>

Ajp-request 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

See Also

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

Visit Nmap NSE Library for more scripts.

The ajp-request.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 AJP server

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

57:	
58:	action = function(host, port)
59:	
60:	  local helper = ajp.Helper:new(host, port)
61:	  if ( not(helper:connect()) ) then
62:	    return fail("Failed to connect to AJP server")
63:	  end
64:	
65:	  local valid_methods = {
66:	    ["GET"]    = true,
67:	    ["HEAD"]   = true,

Method not supported: %s

Here is a relevant code snippet related to the "Method not supported: %s" error message:

71:	    ["OPTIONS"]= true,
72:	  }
73:	
74:	  local method = arg_method:upper()
75:	  if ( not(valid_methods[method]) ) then
76:	    return fail(("Method not supported: %s"):format(arg_method))
77:	  end
78:	
79:	  local options = { auth = { username = arg_username, password = arg_password } }
80:	  local status, response = helper:request(arg_method, arg_path, nil, nil, options)
81:	  if ( not(status) ) then

Failed to retrieve response for request

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

77:	  end
78:	
79:	  local options = { auth = { username = arg_username, password = arg_password } }
80:	  local status, response = helper:request(arg_method, arg_path, nil, nil, options)
81:	  if ( not(status) ) then
82:	    return fail("Failed to retrieve response for request")
83:	  end
84:	  helper:close()
85:	
86:	  if ( response ) then
87:	    local output = response.status_line .. "\n" ..

Failed to open file %s for writing

Here is a relevant code snippet related to the "Failed to open file %s for writing" error message:

88:	      table.concat(response.rawheaders, "\n") ..
89:	      (response.body and "\n\n" .. response.body or "")
90:	    if ( arg_file ) then
91:	      local f = io.open(arg_file, "w")
92:	      if ( not(f) ) then
93:	        return fail(("Failed to open file %s for writing"):format(arg_file))
94:	      end
95:	      f:write(output)
96:	      f:close()
97:	      return ("Response was written to file: %s"):format(arg_file)
98:	    else

Version

This page has been created based on Nmap version 7.92.

Go back to menu.