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

Security Advisories Relating to Symantec Products - Symantec Security Information Manager Console Security Issues


July 1, 2013








Base Score



CVSS2 Vector

Symantec Security Information Manager (SSIM) Java Console XSS - Medium





Symantec Security Information Manager (SSIM) SQL Injection - Medium





Symantec Security Information Manager (SSIM) Information Disclosure - Low






Symantec's Security Information Manager (SSIM) management console is susceptible to  multiple security issues.   Successful exploitation could result in potential cookie stealing, session hijacking, unauthorized disclosure of sensitive application information and potential for unauthorized database manipulation.


Product(s) Affected





Symantec Security Information Manager Appliance



Update to SSIM 4.8.1

Symantec Security Information Manager Appliance



Update to SSIM 4.8.1



Symantec was notified of multiple security issues impacting the SSIM management console.

Cross-site scripting, both reflected and stored are present in some SSIM console interface pages.  These result from insufficient validation/sanitation of client input and application output.  Successfully targeting of these XSS instances would require malicious script be hosted on a network client system to attempt to target the SSIM console during a manual or scheduled network scan.  This could be accomplished by a malicious authorized network user placing arbitrary script on a network client.  Or, by enticing an authorized client user to follow a link or visit a web page hosting malicious script that could be downloaded to the client system.      Successful exploitation could possibly result in stealing user cookies or potentially leveraged to hijack an authorized user session.


The SSIM console does not properly restrict queries to web-GUI APIs which could be manipulated to potentially disclose sensitive information to unauthorized network users.  This information could possibly be leveraged in any follow-on attempts to further compromise the application or network. 


The SSIM console does not sufficiently sanitize authorized client queries made against the database. A malicious user who has or can gain authorized access to a valid account could potentially inject arbitrary SQL database queries in attempts to further compromise the database.  




Symantec Response

Symantec engineers verified these submitted issues as being identified during recent internal review. They have been addressed in Symantec Security Information Manager 4.8.1.  

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

Symantec Security Information Manager 4.8.1 is currently available through normal update channels.


Best Practices

As part of normal best practices, Symantec strongly recommends:

·         Restrict access to administration or management systems to privileged users.

·         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 credits  Hacktive Security Research and Development team for reporting these issues to us and coordinating with us as we resolved them. 



BID: Security Focus, http://www.securityfocus.com, has assigned a 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. 







BID 60796

SSIM Java Console SQL Injection


BID 60797

SSIM Java Console XSS


BID 60798

SSIM Java Console Information Disclosure





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