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

Security Advisories Relating to Symantec Products - Symantec IM Manager Local-Access Cross-site Scripting


February 18, 2010

Revision History



Remote Access Yes (adjacent network)
Local Access no
Authentication Required yes
Exploit publicly available no


Symantec’s IM Manager management console is susceptible to a cross-site scripting issue.

Affected Product(s)

Product Version Solution(s)
Symantec IM Manager 8.3 and 8.4 Upgrade to 8.4.13

Note: Customers running 8.3 versions of Symantec IM Manager should upgrade to the latest 8.4 release and apply all available updates.


Symantec was notified of a cross-site scripting issue present in the Symanec IM Manager console. The console fails to properly filter/ validate external input from non-privileged users with authorized access to the console. This could result in unauthorized access to other users’ session cookies or to unauthorized network information.

Symantec Response

Symantec product engineers have verified the issue and released a fix for affected product versions. Symantec recommends all customers apply the latest available update to protect against threats of this nature.

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

Symantec recommends all customers apply the fix, Symantec IM Manager 8.4.13, available through the FileConnect -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.
  • 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 would like to thank Rafael B. Brinhosa, Security Researcher, rafael.brinhosa@infoseguranca.com.br for reporting this issue and coordinating with us while Symantec resolved it.


BID: Security Focus, http://www.securityfocus.com, has assigned a Bugtraq ID (BID) to this issue for inclusion in the Security Focus vulnerability database.
BID 38241 is assigned to the cross-site scripting issue

CVE: This issue are candidates for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems. The CVE initiative has assigned CVE-2009-3036 to this 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.
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: February 18, 2010
Security Response Blog
The State of Spam