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

Security Advisories Relating to Symantec Products - Input validation errors in SYMLTCOM.dll can lead to a buffer overflow.


February 17, 2010

Revision History




Remote Access Yes
Local Access No
Authentication Required No
Exploit publicly available No


Norton and Symantec products that utilize SYMLTCOM.dll are susceptible to input validation errors that can lead to a buffer overflow.

Affected Product(s)

Product Version Solution(s)
N360 1.0 and 2.0

Run LiveUpdate in interactive mode

Norton Internet Security

2006 through 2008

Norton AntiVirus
Norton SystemWorks
Norton Confidential
Symantec Client Security 3.0.x Upgrade to SCS 3.1 MR9
3.1.x Upgrade to MR9


Symantec was notified of a browser-based ActiveX input validation issue in SYMLTCOM.dll that can potentially be used to produce a buffer overflow. Improperly validated information sent to the .dll can reduce the stability of the products by overwriting unauthorized portions of memory. This failure could potentially result in a browser crash or, possibly unauthorized use of methods allowing access to system information. If successfully exploited, this issue could result in a stack overflow with the potential for malicious code execution in the context of the user’s browser.

The impact of this threat is considerably lessened as it requires leveraging other vulnerabilities to gain access to the system. It can only be used against a specific domain.

To exploit successfully, an attacker would need to be able to effectively masquerade as an authorized site and entice a user to click on their specific URL for the malicious code to successfully impact the customer’s system.

Symantec Response

Symantec product engineers have released a fix via LiveUpdate for affected Norton Consumer products and a fix in MR9 for affected Symantec Enterprise Products. Symantec recommends all customers apply the latest available updates to protect against threats of this nature.

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


Symantec Security Response has released an IPS signature,

23214 - HTTP Symantec NAV ActiveX BO

to detect and block attempts to exploit this issue. Signature will be available through normal updates.

Best Practices

As part of normal best practices, Symantec strongly recommends:

  • Restrict access to administration or management systems to privileged users.
  • Restrict remote access, if required, 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 VUPEN Security(http://www.vupen.com) for reporting this issue and coordinating with Symantec to resolution.


BID: Security Focus, http://www.securityfocus.com, has assigned a Bugtraq ID (BID) 38217 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. CVE-2010-0107 has been assigned to the 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: February 17, 2010
Security Response Blog
The State of Spam