Revision History None
|Exploit publicly available
Overview Norton and Symantec products that utilize SYMLTCOM.dll are susceptible to input validation errors that can lead to a buffer overflow.
||1.0 and 2.0
Run LiveUpdate in interactive mode
|Norton Internet Security
2006 through 2008
|Symantec Client Security
||Upgrade to SCS 3.1 MR9
||Upgrade to MR9
Details 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.
Mitigations 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.
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.
Security Focus, http://www.securityfocus.com
, has assigned a Bugtraq ID (BID) 38217 to these issues for inclusion in the Security Focus vulnerability database.
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.
REPORTING VULNERABILITIES TO SYMANTEC
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 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 firstname.lastname@example.org
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 email@example.com
The Symantec Software Security PGP key can be found at the following location:
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 Software Security. Reprinting the whole or part of this alert in any medium other than electronically requires permission from firstname.lastname@example.org