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

Security Advisories Relating to Symantec Products - Symantec Endpoint Protection Manager/Protection Center 12.x Buffer Overflow


June 18, 2013


6/19/2013 Including Symantec Endpoint Protection Center (SPC) 12.0 Small Business Edition in affected products. 





Base Score



CVSS2 Vector

SEPM/SPC Secar.dll Buffer Overflow - High






A dynamic link library (dll) in the Symantec Endpoint Protection Manager (SEPM) 12.1.x server and Symantec Protection Center (SPC) 12.0.x Small Business Edition server does not properly validate all external input. This could potentially result in a buffer overflow and remote code execution with application privileges on the system that is hosting the management server. 

Affected Products





Symantec Endpoint Protection Manager (SEPM) Console



Upgrade to SEP 12.1.3 (RU3)

Symantec Endpoint Protection Center (SPC) Small Business Edition Console




Migrate to SEP 12.1.3 (RU3)

Products Not Affected



Symantec Endpoint Protection Manager





Symantec was notified of a pre-authentication buffer overflow found in the Symantec Endpoint Protection Manager (SEPM) 12.1.x and Symantec Endpoint Protection Center (SPC) 12.0.x Small Business Edition. Insufficient bounds checking is done on external input by the secars.dll which could result in overflowing the existing buffer and possible remote code execution on the server if successfully exploited. This could enable an authorized network user or an unauthorized individual who can gain access to the network to attempt to leverage this issue to elevate privileges on the SEPM or SPC server via the client/server comms port. In a recommended installation, the Symantec Endpoint Protection Manager/SPC server should not be accessible external to the network.

Symantec is not aware of any customers affected by this issue or any malicious attempts to exploit this issue.

Symantec Response
Symantec product engineers verified the reported issue and that it is resolved in the Symantec Endpoint Protection 12.1.3 (RU3) release.

Update Information

Updates are available through customers' normal support/download locations.


Symantec Security Response will release IPS signature 26667 "Web Attack: Symantec Endpoint Remote Code Exec" that detects and blocks attempts to exploit this issue. Signatures are available through normal Symantec updates.

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 credits
Jerome Nokin, Verizon Enterprise Solutions (GCIS Threat and Vulnerability Management) for discovering this vulnerability and Thierry Zoller, Verizon Enterprise Solutions (GCIS Threat and Vulnerability Management) for reporting and coordinating this issue with us while it was resolved.



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 60542

SEPM/SPC Secars.dll Buffer Overflow Remote Code Execution




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