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

Security Advisories Relating to Symantec Products - Symantec Endpoint Protection Local Client Application Device Control Buffer Overflow


August 4, 2014








Base Score



CVSS2 Vector

SEP Local Client ADC Buffer Overflow- Medium






Symantec is aware of a local access Symantec Endpoint Protection (SEP) client buffer overflow exploit that has been released publicly which could potentially cause a BSOD on the client or possibly allow unauthorized local privilege elevation on Symantec Endpoint Protection (SEP) clients. 

Affected Products





Symantec Endpoint Protection Client



Update to 12.1 RU4 MP1b.  Follow recommended mitigation until update is installed

Symantec Endpoint Protection Client



Update to 12.1 RU4 MP1b.  Follow recommended mitigation until update is installed

Symantec Endpoint Protection 12.0 Small Business Edition



update to latest available build of SEP 12.1 Small Business Edition

Product Not Affected



Symantec Endpoint Protection Manager


Symantec Endpoint Protection 12.1 Small Business Edition


Symantec Endpoint Protection.cloud (SEP SBE)


Symantec Network Access Control (SNAC)




The sysplant driver, loaded as part of the Application and Device Control (ADC) component on a SEP client, does not do sufficient validation of external input which could result in a local client BSOD denial of service or, if successfully exploited, potentially local elevation of privilege on the client system.

Symantec Response
Symantec product engineers verified this issue and have created an update to resolve it.
Customers should use the mitigation described below until the available update can be installed to address this issue.  Symantec is not aware of exploitation of or adverse customer impact from this issue.

Update Information

Please see TECH223338 for further information on language and build availability for Symantec Endpoint Protection update 12.1 RU4 MP1b.



If unable to apply the update immediately, SEP administrators can uninstall or disable ADC in SEP 12.1 or SEP 11.0 by following the instructions provided in KB Article, TECH223338


Symantec Security Response has released Bloodhound.Exploit.554 for this type of issue. This detection is available through normal Symantec security updates.

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 CERT/CC for reporting this issue from Offensive Security to Symantec and coordinating with us. Symantec further thanks Matteo Memelli, Offensive Security for providing coordination to confirm the issues were addressed.



BID: Security Focus, http://www.securityfocus.com, has assigned Bugtraq IDs (BIDs) 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. 






BID 68946

SEP Local Client ADC Buffer Overflow





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.
Please contact secure@symantec.com if you feel you have discovered a security issue in a Symantec product. A member of the Symantec Product 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 Product Security PGP key can be found at the location below.
Symantec has developed a Product Vulnerability Response document outlining the process we follow in addressing suspected vulnerabilities in our products. This document is available below.

Copyright (c) by Symantec Corp.

Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Product Security. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com


The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Product Security, and secure@symantec.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.
* Signature names may have been updated to comply with an updated IPS Signature naming convention. See http://www.symantec.com/business/support/index?page=content&id=TECH152794&key=54619&actp=LIST for more information.
Last modified on: August 4, 2014
Security Response Blog
The State of Spam