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

Security Advisories Relating to Symantec Products - Symantec IM Manager Eval() Code Injection


January 31, 2011

Revision History




CVSS2 Base Score: 8.2

Impact 9.5, Exploitability 6.8

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

Exploit Publicly Available: No


Symantec’s IM Manager Administration console is susceptible to an eval() code injection which could result in remote code execution leading to possible compromise of the Symantec IM Manager application.

Affected Product Version(s)

Symantec IM Manager versions up to 8.4.16 are affected.


Symantec was notified of an eval() code injection issue in Symantec IM Manager Administration console. The console fails to properly validate user input. If successful, a remote attacker could potentially run arbitrary code leading to possible compromise of the Symantec IM Manager application. In order for this attack to be successful, an attacker would need to entice a logged-in console user to visit a malicious link.

Symantec Response

Symantec engineers have verified this issue and released an update to address it. Symantec engineers did additional in-depth reviews of related functionality to further enhance the overall security of Symantec IM Manager.

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

Symantec recommends all customers upgrade to Symantec IM Manager - 8.4.17, 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.
  • 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


Andrea Micalizzi reported this through TippingPoint’s ZeroDay Initiative. Symantec would like to thank TippingPoint ZDI for reporting the issue and providing co-ordination 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 is 45946.

CVE: This issue is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems. The CVE initiative has assigned CVE-2010-3719.


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