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

Security Advisories Relating to Symantec Products - Symantec IT Management Suite Multiple Issues


October 31, 2016

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




Symantec has released updates to address two security issues: a cross-site scripting (XSS) issue and a denial of service (DoS) issue reported in the Symantec IT Management Suite (ITMS) workflow process manager console.


Highest severity issue: Medium
Number of issues: 2


< Back to top




This update applies to the following issues:




Symantec IT Management Suite Workflow Process Manager Console Reflected XSS



Symantec IT Management Suite Workflow Process Manager Console DoS




< Back to top




Symantec has verified the issues and addressed them in product updates, outlined as follows:



The following Symantec enterprise products are affected.



Symantec IT Management Suite 8.0

ITMS 8.0 HF4


< Back to top





Symantec IT Management Suite Workflow Process Manager Console XSS


BID: 93952

Severity: Medium (CVSSv3: 6.7) AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

Impact: Cross site scripting

Exploitation: None


Symantec was notified of a reflected cross-site scripting (XSS) issue found in the ITMS 8.0 workflow process manager console. This was due to the failure to properly filter user-supplied input during an HTTP request to the workflow process manager console.


XSS issues are the result of insufficient validation/sanitation of user input and server output. A successful exploitation of this type of issue is possible should a properly authenticated user click on a maliciously crafted link or an authenticated user with access to the management console submit a specifically formatted HTTP request. Depending on the nature of the link, it is possible for arbitrary HTML requests and scripts to be executed in the context of the user, potentially allowing unauthorized access to or modification of ITMS information.

If an external attacker wanted to take advantage of this issue, they would need to successfully entice an authorized console user to visit a malicious website or click a malicious HTML link in an email.

In a typical installation, the Symantec ITMS workflow process manager console should not be accessible outside of the network environment, and access should be restricted to specified users/administrators. Web browsers used by authorized users to manage the Symantec ITMS workflow process manager should never be used to browse external websites during an active administrative session. These restrictions greatly reduce exposure to external exploit attempts.


Symantec IT Management Suite Workflow Process Manager Console DoS


BID: 93951

Severity: Low (CVSSv3: 3.0) AV:A/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L

Impact: Denial of service

Exploitation: None

The ITMS workflow process manager console login window does not properly sanitize user input. An authorized network user with access to the workflow process manager console application could potentially input large quantities of data. This could cause reduced responsiveness in the workflow process manager console application’s functionality.


< 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




  • Marcin Zięba of Prevenity.com (CVE-2016-6588, CVE-2016-6589)



< 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: October 31, 2016
Security Response Blog
The State of Spam