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

Security Advisories Relating to Symantec Products - Symantec IM Manager Administrator Console Multiple Issues


September 29, 2011

Revision History






CVSS2 scoring for Code Injection

CVSS2 Base Score: 7.6

Impact 9.5, Exploitability 5.5

CVSS2 Vector:  AV:A/AC:M/Au:S/C:P/I:P/A:P

Exploit Publicly Available:  No



CVSS2 scoring for Cross-Site Scripting and SQL Injection

CVSS2 Base Score: 6

Impact 6.4, Exploitability 6.8

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

Exploit Publicly Available:  No



Symantec IM Manager is vulnerable to Code Injection, Cross-Site Scripting and SQL Injection. Successful exploitation of these vulnerabilities could result in injection/execution of arbitrary code in the context of the browser or the application.


Product Affected




 Symantec IM Manager

 8.4.17 and prior

 Update to 8.4.18



Symantec was notified of Cross-Site Scripting and Code injection/execution issues present in the Symantec IM Manager management console. The management console fails to properly filter/validate external inputs.
Successful exploitation of SQL Injection or Remote Code execution might possibly lead to compromise of database or application
Additionally, successful exploitation of Cross-Site Scripting could possibly lead to unauthorized access to users' session cookies or to unauthorized network information.
 In normal installations, the management console is not reachable from outside the network. Hence an authorized but unprivileged network user is required to exploit these issues or to be enticed to visit a malicious link.


Symantec Response

Symantec engineers have verified these issues and released updates to address them. Symantec engineers did additional reviews of related functionality to further enhance the overall security of Symantec IM Manager. Necessary updates have been released.

Symantec is not aware of any exploitation of, or adverse customer impact from this issue.

Symantec recommends all customers upgrade to Symantec IM Manager - 8.4.18, available through theFileConnect-Electronic Software Distribution web site.


Best Practices

As part of normal best practices, Symantec strongly recommends:

  • Restrict access to administration or management systems to privileged users.
  • Disable remote access or restrict it to trusted/authorized systems 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


Sow Ching Shiong reported Cross-Site Scripting and SQL Injection through Secunia Research. Andrea Micalizzi, aka rgod, reported code injection issues through TippingPoint's ZeroDay Initiative. Symantec would like to thank Secunia Research and TippingPoint ZDI for reporting these issues and providing co-ordination while Symantec 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.
BID 49739 has been assigned to the Cross-Site Scripting issue and BID 49738 has been assigned to the SQL Injection issue reported through Secunia Research.

BID 49742 has been assigned to the code injection issues reported through ZDI.

CVE: These issues are 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-0552 to the Cross-Site Scripting issue, CVE-2011-0553 to the SQL injection issue, and CVE-2011-0554 to the Code Injection issue.

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: September 29, 2011
Security Response Blog
The State of Spam