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

Security Advisories Relating to Symantec Products - Symantec Altiris Deployment Solution and Notification Server Management Console FileDownload Vulnerability

SYM09-013

September 22, 2009

Revision History

10/09/2009, Updated the CVE ID. Should read CVE-2009-3028 vice CVE-2009-0328

Severity

Medium


Remote Access

Yes

Local Access

No

Authentication Required

No

Exploit publicly available

Yes

Overview

Symantec’s Altiris Deployment Solution and Notification Server install a vulnerable ActiveX control. Exploitation of this issue could possibly lead to unauthorized information disclosure, system information corruption or potentially allow arbitrary code execution in the context of the user’s browser. Successful exploitation would require user interaction.

Affected Product(s)

Product Version Build Solution(s)
Altiris Deployment Solution 6.9.x All Apply Hotfix per KB
Altiris Notification Server 6.0.x All Apply Hotfix per KB

Symantec Management Platform 7.0.x All Apply Hotfix per KB

Details

Symantec is aware of a vulnerable ActiveX control, AeXNSPkgDLLib.dll, being reported in Symantec’s Altiris Deployment Solution. This control also ships with the Altiris Notification Server / Symantec Management Platform. This control was not intended to be called externally. However, it uses an unsafe method that could potentially allow download and possible execution of arbitrary code on the host system. Unauthorized access to the vulnerable control could result in possible arbitrary code execution in the context of the user’s browser. The application this control resides on should not be accessible external to the network in a recommended installation. To attempt to exploit this issue, the host user would need to be enticed to download and execute code by visiting a malicious web site, internal or external to the network, or potentially through an html email that could effectively call the vulnerable control.

Symantec Response

Symantec engineers have verified these findings and released an update to resolve this issue. Symantec is not aware of any customer impact from this issue.

Follow instructions and hotfix provided in Altiris Knowledge Base article 49069, available to customers at https://kb.altiris.com/kb/article/viewArticle.asp?aid=49069

Review the associated Knowledge Base article for information on possible impact of this fix to products built on Notification Server/Symantec Management Platform.

Mitigations

Symantec Security Response has released IPS/IDS signatures,
23473 - HTTP Altiris Express File Overwrite
50235 - MSIE Altiris Express File Overwrite

to detect and block attempts to exploit this issue. Signatures are available through normal update channels.

Workaround

Disable attempts to instantiate the AeXNSPkgDLLib.dll ActiveX control CLSID {63716E93-033D-48B0-8A2F-8E8473FD7AC7} in Microsoft Internet Explorer by manually setting the kill bit for the control in the registry. Follow the steps outlined in Microsoft Knowledge Base Article 240797 to manually set the kill bit for this control.

Important: Symantec strongly recommends that you back up the registry before making any changes to it. Incorrect changes to the registry can result in permanent data loss or corrupted files. Modify the specified keys only. Read the document, "How to make a backup of the Windows registry," for instructions.

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

References:

Security Focus, http://www.securityfocus.com, has assigned Bugtraq ID (BID) 36346 to these issues for inclusion in the SecurityFocus vulnerability database.

This issue is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems. CVE-2009-3028 has been assigned to this 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 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:
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 secure@symantec.com.
Last modified on: September 22, 2009
Security Response Blog
The State of Spam