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

Security Advisories Relating to Symantec Products - Symantec Data Loss Prevention Enforce Server Administration Console Cross-site Scripting, Cross-site Request Forgery Issues


June 22, 2015








Base Score



CVSS2 Vector

Symantec Data Loss Prevention Enforce Server administration console XSS - Medium





Symantec Data Loss Prevention Enforce Server administration console CSRF – Medium







Symantec's Data Loss Prevention (DLP) Management Console is potentially susceptible to persistent cross-site scripting (XSS) issues and a possible cross-site request forgery (CSRF) in the Enforce Server administration console. Successful exploitation could result in potential unauthorized actions directed against the console potentially with elevated privileges.


Affected Products




Symantec Data Loss Prevention

12.5.1 and prior

Migrate to Symantec Data Loss Prevention 12.5.2 or later release



Symantec was notified of XSS issues as well as possible CSRF issues within the Symantec Data Loss Prevention Enforce Server administration console. Additionally, Symantec DLP engineers have been doing extensive internal reviews that identified and addressed other areas susceptible to similar issues. 

Both XSS and CSRF issues are the result of insufficient validation/sanitation of user input and server output. A successful exploitation of these issues in Enforce Server administration console pages used to manage DLP is possible should a properly authenticated user click on a maliciously-crafted link. Depending on the nature of the link it is possible for execution of arbitrary html requests and scripts in the context of the targeted user. The administration console normally allows access to only specified users/administrators with varying levels of access depending on their requirements.

Cross-site scripting and cross-site request forgery are trust exploitations requiring enticing a previously authenticated user to click on a link in a context such as a website URL or an HTML email. To be exposed to other than another authorized network user, an external attacker would need to successfully entice an authorized, privileged or limited-access Enforce Server console user to visit a malicious web site or click on a malicious HTML link in an email in any attempts to take advantage of this issue.

In a typical installation the Symantec Data Loss Prevention Enforce Server administration console should not be accessible external to the network environment and access should be restricted to specified users/administrators. Web browsers used by authorized users to manage Symantec Data Loss Prevention Enforce Server should never be used for casual browsing of external web sites during an active administrative session. These restrictions greatly reduce exposure to external attempts of this type.


Symantec Response
Symantec engineers have verified and addressed these external submissions as well as those identified through internal reviews. Symantec strongly recommends Symantec Data Loss Prevention customers update to the latest release of Symantec Data Loss Prevention as indicated in the above product table. Symantec knows of no exploitation of or adverse customer impact from these issues.

Symantec Data Loss Prevention 12.5.2 and 14.0 are currently available through customer normal download channels.



Since exploitation depends on user interaction (phishing, clicking on untrusted html link), customers are strongly encouraged to follow security best practices.
Specifically, during an active DLP administration session:


  • Avoid casual surfing in different tabs of the browser session
  • Avoid clicking html links in emails or any other electronic document that may launch an additional browser instance

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

  • Restrict access to administration or management systems to privileged users.
  • Avoid casual surfing in different tabs when using the browser to administer systems.
  • Do not click on html links in emails.
  • Disable remote access if not required or restrict it to trusted/authorized systems only.
  • Where possible, limit exposure of application and web interfaces to trusted/internal networks only.
  • 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 Mike Czumak (@SecuritySift) for reporting XSS and CSRF issues; Pieter Hiele for reporting XSS issues and both for coordinating with us as we resolved them.




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. 








Symantec Data Loss Prevention Enforce Server administration console XSS



Symantec Data Loss Prevention Enforce Server administration console 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: June 22, 2015
Security Response Blog
The State of Spam