1. Symantec/
  2. Security Response/
  3. Security Updates Detail

Security Advisories Relating to Symantec Products - Symantec Messaging Gateway Security Update


September 27, 2016

Overview | Issues | Affected Products | Mitigation | Best Practices | Acknowledgements | Revisions | Reporting Vulnerabilities




Symantec has addressed a directory traversal issue in Symantec Messaging Gateway caused by insufficient sanitization of user-supplied input. This issue could allow unauthorized access to files or directories.


Highest severity issue: Medium
Number of issues: 1


< Back to top




This update applies to the following issues:




Symantec Messaging Gateway Directory Traversal




< Back to top




Symantec has verified the issues and addressed them in product updates as outlined below.



The following Symantec enterprise products are affected.



Symantec Messaging Gateway (SMG) Appliance*

(Prior to SMG 10.6.2)

Upgrade to maintenance release SMG 10.6.2

Available through the software upgrade facility


*Non-appliance versions of Symantec Messaging Gateway are not impacted by this issue.


< Back to top





Symantec Messaging Gateway Directory Traversal


BID: 93148

Severity: Medium (CVSSv3: 4.1) AV:A/AC: L/PR:L/UI:N/S:C/C:L/I:N/A:N

Impact: Directory traversal

Exploitation: None

Date patched: September 19, 2016

A charting component in the Symantec Messaging Gateway control center does not properly sanitize user input submitted for charting requests. This could potentially result in an authorized but less privileged user gaining access to paths outside the authorized directory. This could potentially provide read access to some files/directories on the server for which the user is not authorized.


< Back to top




The listening port for Symantec Messaging Gateway Control Center should not be accessible outside of the authorized network. Restrict access to the Symantec Messaging Gateway Center to network-authorized, control center privileged users only.


< Back to top




Symantec recommends the following measures to reduce risk of attack:

  • Restrict access to administrative or management systems to authorized privileged users.
  • Restrict remote access to trusted/authorized systems only.
  • Run under the principle of least privilege, where possible, to limit the impact of potential exploit.
  • Keep all operating systems and applications current with vendor patches.
  • Follow a multi-layered approach to security. At a minimum, run both firewall and anti-malware applications to provide multiple points of detection and protection to both inbound and outbound threats.
  • Deploy network and host-based intrusion detection systems to monitor network traffic for signs of anomalous or suspicious activity. This may aid in the detection of attacks or malicious activity related to the exploitation of latent vulnerabilities.


< Back to top




  • Rio Sherri of S&T Albania (CVE-2016-5312)


< Back to top




  • September 27, 2016: Fixed the CVE ID under the ISSUES section to reflect CVE-2016-5312, the correctly assigned CVE for this issue.


< Back to top



Symantec takes the security and proper functionality of our products very seriously. As founding members of the Organization for Internet Safety (OISafety), Symantec supports and follows responsible disclosure guidelines.
Symantec has developed a Software Security Vulnerability Management Process document outlining the process we follow in addressing suspected vulnerabilities in our products.
Symantec Corporation firmly believes in a proactive approach to secure software development and implements security review into various stages of the software development process. Additionally, Symantec is committed to the security of its products and services as well as to its customers’ data. Symantec is committed to continually improving its software security process.
This document provides an overview of the current Secure Development Lifecycle (SDLC) practice applicable to Symantec’s product and service teams as well as other software security related activities and policies used by such teams. This document is intended as a summary and does not represent a comprehensive list of security testing and practices conducted by Symantec in the software development process.
Please contact secure@symantec.com if you believe you have discovered a security issue in a Symantec product. A member of the Symantec Software Security team will contact you regarding your submission to coordinate any required response. Symantec strongly recommends using encrypted email for reporting vulnerability information to secure@symantec.com.
The Symantec Software Security PGP key can be found at the following location:
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Software Security. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com.
Last modified on: September 27, 2016
Security Response Blog
The State of Spam