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

Security Advisories Relating to Symantec Products - Symantec Management Console Directory Traversal


November 20, 2017

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




Symantec has released an update to address an issue in the Symantec Management Console product.


Highest severity issue: High
Number of issues: 1


< Back to top




This update applies to the following issues:




Symantec Management Console 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 Management Console prior to ITMS 8.1 RU4, ITMS 8.0 POST HF6 & ITMS 7.6 POST HF7

Upgrade to Symantec Management Console version ITMS 8.1 RU4 or apply patches ITMS 8.0 POST HF6 & ITMS 7.6 POST HF7 to previous releases


< Back to top





Symantec Management Console Directory Traversal


BID: 101743

Severity: High (CVSSv3: 7.6) AV:A/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

Impact: Directory traversal

Exploitation: None

Date patched: November 17, 2017

The Symantec Management Console can be susceptible to a directory traversal exploit, which is a type of attack that can occur when there is insufficient security validation / sanitization of user-supplied input file names, such that characters representing "traverse to parent directory" are passed through to the file APIs. The goal of this attack is to use an affected application to gain unauthorized access to the file system.



< Back to top




This issue was validated by the product team engineers. A Symantec Management Console update, version ITMS 8.1 RU4 as well as patches ITMS 8.0 POST HF6 & ITMS 7.6 POST HF7, have been released which address the aforementioned issue. Note that the latest Symantec Management Console release and patches are available to customers through normal support channels. At this time, Symantec is not aware of any exploitations or adverse customer impact from this issue.


< 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




  • Christoffer Wiman (CVE-2017-15527)



< Back to top




  • None



< 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: November 20, 2017
Security Response Blog
The State of Spam