-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

===========================================================================
             AUSCERT External Security Bulletin Redistribution

                               ESB-2010.0179
   Input validation errors in SYMLTCOM.dll can lead to a buffer overflow
                             19 February 2010

===========================================================================

        AusCERT Security Bulletin Summary
        ---------------------------------

Product:           N360 1.0
                   N360 2.0
                   Norton Internet Security 2006
                   Norton Internet Security 2007
                   Norton Internet Security 2008
                   Norton AntiVirus
                   Norton SystemWorks
                   Norton Confidential
                   Symantec Client Security 3.0.x
                   Symantec Client Security 3.1.x
Publisher:         Symantec
Operating System:  Windows
Impact/Access:     Execute Arbitrary Code/Commands -- Remote with User Interaction
                   Denial of Service               -- Remote with User Interaction
                   Unauthorised Access             -- Remote with User Interaction
Resolution:        Patch/Upgrade
CVE Names:         CVE-2010-0107  

Original Bulletin: 
   http://www.symantec.com/business/security_response/securityupdates/detail.jsp?fid=security_advisory&pvid=security_advisory&year=2010&suid=20100217_01

- --------------------------BEGIN INCLUDED TEXT--------------------

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

February 17, 2010

Description

Revision History
None

Severity
Medium

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

Overview
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
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 users 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 customers 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.

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

Credit
Symantec would like to thank VUPEN Security(http://www.vupen.com) for reporting 
this issue and coordinating with Symantec to resolution.

References
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 the OISafety responsible disclosure 
guidelines. Symantec also subscribes to the vulnerability disclosure 
guidelines outlined by the National Infrastructure Advisory Council (NIAC).

Please contact secure@symantec.com if you feel you have discovered a security 
issue in a Symantec product. A Symantec Product Security team member will 
contact you regarding your submission. 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 end of this message.

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 Security Response. 
Reprinting the whole or part of this alert in any medium other than 
electronically requires permission from secure@symantec.com

Disclaimer
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 Security Response, 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.

Last modified on: February 17, 2010

- --------------------------END INCLUDED TEXT--------------------

You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.

NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members.  As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.

NOTE: This is only the original release of the security bulletin.  It may
not be updated when updates to the original are made.  If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.

Contact information for the authors of the original document is included
in the Security Bulletin above.  If you have any questions or need further
information, please contact them directly.

Previous advisories and external security bulletins can be retrieved from:

        http://www.auscert.org.au/render.html?cid=1980

If you believe that your computer system has been compromised or attacked in 
any way, we encourage you to let us know by completing the secure National IT 
Incident Reporting Form at:

        http://www.auscert.org.au/render.html?it=3192

===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072

Internet Email: auscert@auscert.org.au
Facsimile:      (07) 3365 7031
Telephone:      (07) 3365 4417 (International: +61 7 3365 4417)
                AusCERT personnel answer during Queensland business hours
                which are GMT+10:00 (AEST).
                On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967

iD8DBQFLffRr/iFOrG6YcBERAlctAJ9/s3HSfOemVYsgXnF6nFEcXvkbCgCg0psS
SOChciY+DXcdhYwQaxUgA2U=
=/D7O
-----END PGP SIGNATURE-----