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

Security Advisories Relating to Symantec Products - Altiris Deployment Solution Multiple Vulnerabilities


May 14, 2008

Revision History

May 15, 2008 - Public code has been made available


One High severity issue
Five Medium severity issues
Remote AccessYes (authorized network access required)
Local AccessYes
Authentication RequiredNo
Exploit publicly availableYes, (for Sybsecurity reported issues)


Multiple vulnerabilities were reported in Altiris Deployment Solution. Exploitation of these issues could possibly lead to unauthorized information disclosure, system information corruption or, with the most severe, potentially allow remote access arbitrary code execution with elevated privileges.

Affected Products

Altiris Deployment Solution6.8.x & 6.9.xAll builds prior to 6.9.1766.9.176


3Com Zero Day Initiative (ZDI) reported two issues:
  1. Altiris Deployment Solution is susceptible to an SQL injection vulnerability. The vulnerability, if successfully exploited, could potentially allow a user with authorized network access to run arbitrary code on a targeted system. Issue severity: High.
  2. A remote user with authorized network access could potentially request and obtain encrypted Altiris Deployment Solution domain credentials without being required to properly authenticate on the targeted system. Due to weaknesses in the encryption, this could potentially result in the unauthorized exposure of these domain credentials. Issue severity: Medium.
Sybsecurity reported four issues:
  1. A non-privileged user with authorized access on a targeted system could potentially leverage the Altiris Deployment Solution’s Agent’s user interface to access a privileged command prompt. Issue severity: Medium.
  2. A non-privileged user could leverage a common graphical user interface element (tooltip) to potentially access a command prompt running under elevated user privileges. Issue severity: Medium
  3. The Altiris Deployment Solution creates several registry keys with insufficient access security. Any user with access to a targeted system could potentially modify or delete these registry keys, resulting in possible unauthorized access to system information or disruption of service. Issue severity: Medium.
  4. A system user with access to the install directory of Deployment Solution could potentially replace application components with arbitrary code that could run with administrative privileges on the targeted system. Issue severity: Medium.

Symantec Response

Symantec engineers have verified these issues in all versions of Altiris Deployment Solution prior to version 6.9.176 . Customers currently using version 6.8 should upgrade to 6.9 and apply all hotfixes.
Proof-of-concept code has been released for the issues identified by Sybsecurity.com .Symantec currently knows of no adverse customer impact from these issues.

The following steps are required to access and install the hotfix:
  • Search for KB 41418.
  • Select KB link and download upgrade/hotfix file.
  • After downloading the file, execute and follow the installer instructions to upgrade Deployment Solution.
Note: This hotfix will require a rollout of upgraded DS Agent software.

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


SecurityFocus, http://www.securityfocus.com, has assigned a Bugtraq ID (BID) to this issue for inclusion in the SecurityFocus vulnerability database.The BIDs assigned are 29198, 29199, 29194, 29218, 29196, and 29197.


Symantec credits Brett Moore of Insomnia Security, working through 3Com ZDI (Zero Day Initiative) for reporting these issues and for providing full coordination while Symantec resolved them.
Symantec credits Alex Hernandez of sybsecurity.com and Eduardo Vela for reporting these issues and for providing full coordination while Symantec resolved them.


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: May 14, 2008
Security Response Blog
The State of Spam