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

Security Advisories Relating to Symantec Products - DLL Loading Issue in Symantec Enterprise Products


November 15, 2016

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




Symantec has released updates to address a DLL loading issue in Symantec IT Management Suite (ITMS), Symantec Ghost Solution Suite (GSS), Symantec Encryption Desktop (SED), and Symantec Endpoint Virtualization (SEV).


Highest severity issue: High
Number of issues: 1


< Back to top




This update applies to the following issues:




DLL Loading in Symantec ITMS, GSS, SED, and SEV




< 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 IT Management Suite 8.0 prior to ITMS 8.0 HF4

Update to ITMS 8.0 HF4

Symantec IT Management Suite 7.6 prior to ITMS 7.6 HF7

Update to ITMS 7.6 HF7 and apply point fix (see Mitigations below)

Symantec Ghost Solution Suite 3.1 prior to GSS 3.1 MP4

Update to GSS 3.1 MP4

Symantec Endpoint Virtualization 7.x prior to SEV 7.6 HF7

Update to SEV 7.6 HF7

Symantec Encryption Desktop 10.x prior to SED 10.4.1 MP1

Update to SED 10.4.1 MP1


< Back to top





DLL Loading in Symantec ITMS, GSS, SED and SEV


BID: 94279

Severity: High (CVSSv3: 7.3) AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Impact: Code execution

Exploitation: None


Symantec was notified of a DLL loading issue impacting the Symantec ITMS, GSS, SED and SEV products. An authorized but non-privileged user could potentially leverage this issue to execute arbitrary code with elevated privileges on the system. Ultimately, this problem is caused by a failure to use an absolute path when loading DLLs during product boot up/reboot. This can cause default DLL search logic to be followed and creates the potential for an unauthorized execution of a specifically-crafted DLL substituted for the authorized DLL in the search path. If successfully accomplished, the user's code could potentially execute with the elevated privileges of the application.

An external attacker would need to successfully entice an authorized user to visit a malicious web site or click on a malicious HTML link in an email in any attempts to download malicious code to take advantage of this issue.


< Back to top




Symantec engineers verified this finding and have resolved it in the product upgrades indicated as solutions in the Affected Products table. For customers with Symantec IT Management Suite 7.6, ensure you update to ITMS 7.6 HF7 and then apply point fix as described in https://support.symantec.com/en_US/article.info3459.html. Product Updates are available through normal customer product download locations.

Customers should apply these upgrades to avoid potential incidents of this nature.

Symantec is not aware of exploitation of 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




  • Himanshu Mehta (CVE-2016-6590)
  • Praveen Singh (CVE-2016-6590)


< Back to top




  • December 19, 2016: Added ITMS 7.6 releases prior to 7.6 HF7 to the affected products along with mitigation steps for ITMS 7.6 HF7
  • March 31, 2017: Added SED 10.x prior to SED 10.4.1 MP1 to the affected products with solution upgrade to SED 10.4.1 MP1


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