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

Security Advisories Relating to Symantec Products - Symantec Deployment Solution AClient Memory Overwrite


December 19, 2014








Base Score



CVSS2 Vector

Symantec Deployment Solution Memory Overwrite   - Medium






Exploit Publicly Available:  No



An arbitrary memory overwrite vulnerability exists in a Symantec Deployment Solution agent allowing a local and authorized malicious user to potentially elevate privileges on the local system.  This vulnerability applies to Windows XP (SP3) or Windows Server 2003 (SP2) only.


Affected Products





Symantec Deployment Solution

6.9 and prior



Use DAgent and disable use of AClient (See mitigation URL below for more information)



A Symantec Deployment Solution agent driver, AClient, is susceptible to a buffer overflow resulting from a malicious user with local access being able to potentially overwrite memory, possibly resulting in an escalation of privilege on the system. 


NOTE:   This issue can only be exploited on Windows XP and Windows Server 2003 as newer Windows operating systems have different verification methodologies and so are not impacted by this issue.


Successful exploitation could potentially allow a local user to gain unauthorized access to resources on the targeted system, interfere with communications between the client and server or, disrupt or modify the capability of the management server to effectively monitor and manage the client system.


Symantec Response
Symantec engineers have reviewed and validated this issue as impacting versions  of Deployment Solution 6.9 on Windows XP and Windows Server 2003 only. 


Symantec recommends customers disable use of Deployment Solution 6.9 AClient and enable the DAgent.


Symantec is not aware of exploitation of or adverse customer impact from this issue.


Mitigation Information

Please refer to Knowledge Base article, DOC7993, “Arbitrary Write Privilege Escalation in Altiris AClient agent” for more information.


Best Practices
As part of normal best practices, Symantec strongly recommends that customers:

          Restrict access of 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 thanks Parvez Anwar (@parvezghh) for
reporting this issue and for working with us as we resolved the issue.




BID: 71727


CVE: The issue is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems.






BID 71727

Symantec Deployment Solution  






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: December 19, 2014
Security Response Blog
The State of Spam