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

Security Advisories Relating to Symantec Products - Symantec Data Insight Management Console HTML Injection and Cross-Site Scripting


June 25, 2014



06/27/2014 Change CVE for the Cross-Site Scripting issue to CVE-2014-3433 vice CVE-2013-3433 as initially posted.





Base Score



CVSS2 Vector

Data Insight Management Console HTML Injection - High





Data Insight Management Console Cross-Site Scripting (XSS) - Medium







The management console for Symantec Data Insight does not sufficiently validate/sanitize arbitrary input in two separate fields within the management GUI. This could potentially allow unauthorized command execution or potential malicious redirection.

Affected Products





Symantec Data Insight



Symantec Data Insight 4.5

Symantec Data Insight


All prior to 4.5

Symantec Data Insight 4.5



Symantec Data Insight does not properly validate or sanitize external input to user accessible fields on some forms available for use on the management console.

Cross-site scripting and html injection vulnerabilities were reported in forms available through the Symantec Data Insight management console. Cross-site scripting and HTML injection are trust exploitations generally requiring a malicious non-authenticated attacker enticing an authenticated user to click on a malicious link or a malicious network user with authorized or unauthorized access to the vulnerable fields able to inject malicious arbitrary scripts. A successful exploitation, depending on the nature of the attack, could potentially result in arbitrary html scripts executed in the context of the targeted user or the application depending on the vulnerable field being targeted.

In a normal installation, the Symantec Data Insight management console should not be accessible external to the network.  However, an authorized but unprivileged network user or an external attacker able to leverage network access could attempt to exploit these weaknesses.


Symantec Response
Symantec product engineers verified these issues and have released updates to resolve them.
Customers should update to Symantec Data Insight 4.5.

Symantec is not aware of exploitation of or adverse customer impact from these issues.

Update Information

Symantec Data Insight 4.5 is available through Symantec File Connect.


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 thanks the 2am Research team for reporting these issues and working with us as we addressed them.


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 68160

Data Insight Management Interface XSS


BID 68161

Data Insight Management Interface html script injection






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 25, 2014
Security Response Blog
The State of Spam