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

Security Advisories Relating to Symantec Products - Symantec Endpoint Protection Manager Cross-Site Request Forgery and Cross-Site Scripting


January 16, 2012

Revision History




CVSS V2: 6

Impact: 6.44  Exploitability 6.83

CVSS V2 Vector AV: AV:N/AC:M/Au:S/C:P/I:P/A:P

Symantec Endpoint Protection Manager 12.1 web console is susceptible to cross-site scripting and cross-site request forgery that could potentially lead to arbitrary code execution.


Affected Products





Symantec Endpoint Protection



SEP 12.1 RU1 (12.1.1000)

This advisory relates to
SYM11-009 which accurately addressed the vulnerabilities in versions listed at the time. The new assessment shows that Symantec Endpoint Protection 12.1 is also impacted.  This advisory is ONLY for SEP 12.1.  No other versions are impacted.


Symantec was notified of a cross-site scripting and cross-site request forgery vulnerability within the Symantec Endpoint Protection Manager 12.1.  Because both cross-site scripting and cross-site request forgery are trust exploitations, they generally require enticing a previously authenticated user to click on a link in a context such as a website or in an email.


A successful exploitation of these issues is possible once a properly authenticated user clicks on a specially crafted link.  Depending on the nature of the link it is possible for the URL to execute arbitrary html requests and scripts in the context of the targeted user


Symantec Response
Symantec product engineers verified the reported issues.  Symantec engineers fixed the issues in Symantec Endpoint Protection 12.1 RU1.


Symantec knows of no exploitation of or adverse customer impact from these issues.


Update Information

Updates will be available through customers' normal support/download locations. 


Best Practices

As part of normal best practices, Symantec strongly recommends:

  • 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 Ivan Markovic working through
Secunia Labs for identifying these issues and coordinating with Symantec as we resolved them. 

Security Focus,
http://www.securityfocus.com, has assigned Bugtraq ID (BID) 48231 to identify the XSS and 49101 for the CSRF this issue for inclusion in the Security Focus vulnerability database.


CVE: This issue is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems. The CVE initiative has assigned CVE-2011-0550 for XSS and CVE-2011-0551 for CSRF.




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: January 16, 2012
Security Response Blog
The State of Spam