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

Security Advisories Relating to Symantec Products - Symantec Endpoint Protection Multiple Security Issues


March 17, 2016


07/20/2016 - NOTE: CVE-2015-8154 addresses the vulnerability referenced by EnSilo in their blog posting published on July 19, 2016.

03/18/2016 - Added Disable or Uninstall options and instructions for the ADC driver, CVE-2015-8154 in the SEP 12.1 Client


CVSS2 Base Score



CVSS2 Vector






SEPM SQLi - High





SEP Client Security Bypass RWX Permissions SysPlant.sys driver - High






Symantec Endpoint Protection (SEP) was susceptible to a number of security findings that could potentially result in an authorized but less privileged user gaining elevated access to the Management Console. SEP Client security mitigations can potentially be bypassed allowing arbitrary code execution on a targeted client.

Affected Products





Symantec Endpoint Protection Manager and Client



Update to 12.1-RU6-MP4


The management console for SEPM contained a cross-site request forgery vulnerability that was the result of an insufficient security check in SEPM. An authorized but less-privileged user could potentially include arbitrary code in authorized logging scripts. When submitted to SEPM, successful execution could possibly result in the user gaining unauthorized elevated access to the SEPM management console with application privileges.

There was a SQL injection found in SEPM that could have allowed an authorized but less-privileged SEPM operator to potentially elevate access to administrative level on the application.

The sysplant driver is loaded as part of the Application and Device Control (ADC) component on a SEP client if ADC is installed and enabled on the client. A previous security update to this driver did not sufficiently validate or protect against external input. Successfully bypassing security controls could potentially result in targeted arbitrary code execution on a client system with logged-on user privileges. Exploitation attempts of this type generally use known methods of trust exploitation requiring enticing a currently authenticated user to access a malicious link or open a malicious document in a context such as a website or in an email.

NOTE: Customers not using ADC are not impacted by the client issue, CVE-2015-8154. See Mitigations below for information on disabling the ADC driver or uninstalling ADC.

Symantec Response
Symantec product engineers have addressed these issues in SEP 12.1-RU6-MP4. Customers should update to RU6-MP4 as soon as possible to address these issues.

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

Update Information
Symantec Endpoint Protection Manager 12.1-RU6-MP4 is available from Symantec File Connect.


As a workaround against the client issue, CVE-2015-8154, SEP administrators can disable the ADC driver or uninstall ADC in SEP 12.1 by following one of these options

Option 1 for SEP 12.1: Disable the Application and Device Control driver

Note: Deploying an Application and Device Control (ADC) policy is not sufficient to re-enable the driver after it has been disabled. Repairing the installation, or upgrading to a later version, will re-enable the sysplant driver automatically.

  1. From the Symantec Endpoint Protection Management (SEPM) console, withdraw the Application and Device Control policy (if applicable).
  2. Disable or configure Tamper Protection to allow the process for any tools or scripts used.
    How to disable Tamper Protection in Symantec Endpoint Protection 12.1
  3. At the local client, open a Windows command shell with administrative privileges.
  4. Enter the following command:

    sc config sysplant start= disabled

  5. Restart the client computer.
  6. From the SEPM console, enable Tamper Protection.

Option 2 for SEP 12.1: Uninstall Application and Device Control

  1. From the SEPM console, click Admin > Install Packages, click Client Install Feature Set, and select Add Client Install Feature Set.
  2. Choose to remove Application and Device Control, and click OK.
  3. Navigate to Client Groups and select Add Install Packages.
  4. Uncheck Maintain Feature Set, and select the newly created feature set, once for 32-bit and once for 64-bit.
    All SEP clients are moved to that new feature set without the ADC component installed.

Best Practices

As part of normal best practices, Symantec strongly recommends the following:

  • Restrict access to administrative or management systems to authorized 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 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.


Symantec would like to thank Anatoly Katyushin with Kaspersky Labs https://www.kaspersky.com, for finding and reporting CVE-2015-8152, CVE-2015-8153 and working closely with Symantec as they were addressed.

Symantec would like to thank enSilo Research Team, https://www.ensilo.com, for reporting CVE-2015-8154 and working closely with Symantec as it was addressed.


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

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





BID 84343



BID 84354



BID 84344

SEP Client Security Bypass RWX Permissions SysPlant.sys driver


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