Revision History
NoneSeverity
Medium
| Remote Access |
Yes (adjacent network) |
| Local Access |
no |
| Authentication Required |
yes |
| Exploit publicly available |
no |
Overview
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.
Details
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
Credit
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.
References
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.
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.comDisclaimer
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.
Symantec Product Vulnerability Management PGP Key
