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

Security Advisories Relating to Symantec Products - Symantec Endpoint Protection Manager and Client Issues


June 17, 2015









Base Score



CVSS2 Vector

SEPM Auth User Blind SQLi in PHP prepared statements - Medium





Local DoS Deadlock in sysplant.sys prevents system shutdown- Medium





Local Elevation of Privilege DLL loading - Medium







Symantec Endpoint Protection (SEP) 12.1.6 addresses vulnerabilities that were found in prior releases.  These include an authorized but less-privileged administrator able to attempt a blind SQL injection in the SEP Manager (SEPM) console through PHP prepared statements;  a local Denial of Service (DoS) due to the ability to create a deadlock in system functionality preventing complete system shutdown and a local elevation of privilege potential through a dll pre-loading weakness. These issues could result in potential access to unauthorized data, inability to shut down or restart a system without doing a hard power cycle or an authorized but non-privileged user possibly being able to elevate their access to SYSTEM on a local client system.


Affected Products





Symantec Endpoint Protection

12.1.5 and prior


Migrate to SEP 12.1.6



Symantec was notified of security issues that have been addressed with the release of Symantec Endpoint Protection 12.1.6. 

Symantec Endpoint Protection Manager is susceptible to a blind, time-based SQL injection in some interface scripts used to manage the console.  The management console does not provide sufficient validation/sanitation of submitted input.  This could enable an authorized but less-privileged user to potentially run an unauthorized arbitrary SQL query against the backend database.  This would include Limited Administrators as implemented in Symantec Endpoint Protection Manager. This could possibly allow unauthorized access to data or unauthorized manipulation of data.

SEP is susceptible to a local denial of service due to a deadlock condition in sysplant.sys.  A local user can create a local denial of service by running a specifically formatted call resulting in the windows system unable to fully shutdown. Resolution requires a hard power cycle to shut down and restart the system.

SEP is affected by potential dll loading issues resulting from improper path restrictions in some file directories not properly restrict the loading of external libraries.  An authorized malicious local user with access to a system could potentially insert a specifically-crafted file in one of the susceptible directory. Such an attack would then need to entice an authorized user to load a specifically formatted file from an alternate file location or network share.  Successful exploitation could allow unauthorized arbitrary code to be executed with system permissions.


Symantec Response
Symantec product engineers verified these issues.  SEPM 12.1 RU6 contains updates that address these findings.

Symantec is not aware of exploitation of or adverse customer impact from this issue.


Update Information

Symantec Endpoint Protection Manager 12.1 RU6 is available from Symantec File Connect.


Best Practices
Symantec strongly recommends as part of normal best practices:

  • Restrict access to administration or management systems to privileged users.
  • Restrict remote access, if required, to trusted/authorized systems only.
  • Run under the principle of least privilege where possible to limit the impact of exploit by threats.
  • Keep all operating systems and applications updated with the latest vendor patches.
  • Follow a multi-layered approach to security. Run both firewall and anti-malware applications, at a minimum, 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 detection of attacks or malicious activity related to exploitation of latent vulnerabilities.


Symantec would like to thank Knut St. Osmundsen for reporting the deadlock issue, Mike Czumak (@SecuritySift) for reporting the DLL Loading and Jan Kadijk for reporting the Blind SQL Injection and working with us as we addressed these issues.




BID: Security Focus, http://www.securityfocus.com, has assigned Bugtraq ID (BID) to these issues for inclusion in the Security Focus vulnerability database.


CVE: These issues are candidates for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems. 








Local Elevation of Privilege DLL loading



Local DoS Deadlock in sysplant.sys prevents system shutdown



SEPM Auth User Blind SQLi in PHP prepared statements






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: June 17, 2015
Security Response Blog
The State of Spam