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

Security Advisories Relating to Symantec Products - Symantec Altiris Deployment Solution Clear Text Password


April 10, 2008

Revision History



Remote AccessNo
Local AccessYes
Authentication RequiredYes
Exploit publicly availableNo


Symantec’s Altiris Deployment Solution stores the Deployment Solution Agent (AClient) password in clear text in system memory.

Affected Products

Altiris Deployment Solution6.8.xAll6.9.164


Information Risk Management Plc reported that Symantec’s Altiris Deployment Solution stores the AClient password in system memory. A non-privileged local user with authorized access on the targeted system could potentially dump the system memory for AClient.exe and recover the password. The recovered password could then be used to gain access to the local agent admin interface. A successful attack could potentially allow code of the attacker’s choice to be run with system level privileges on the targeted system.

Symantec Response

Symantec engineers have verified and released an update to resolve this issue.

Upgrade to at least version 6.9.164 as follows:
  • Enter your email address.
  • Select "Deployment Solution for Clients 6.9" from the drop-down box
  • Click "Submit"
  • Accept the "End User License Agreement"
  • Click on "Deployment Solution for Clients 6.9" to download a zip file containing the Deployment Solution update.
  • Unzip the update package and double-click on Altiris_DeploymentSolutionWin_6_9.exe.
  • Follow the installation 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


SecurityFocus, http://www.securityfocus.com, has assigned a Bugtraq ID (BID) to this issue for inclusion in the SecurityFocus vulnerability database. The BID assigned is 28707 which can be found at http://www.securityfocus.com/bid/28707

A CVE Candidate name will be requested from the Common Vulnerabilities and Exposures (CVE) initiative for this issue. This advisory will be revised accordingly upon receipt of the CVE Candidate name. This issue is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems.


Symantec would like to thank Mazin Faour with Information Risk Management for reporting this issue and providing full coordination while Symantec resolved it.


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