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

Security Advisories Relating to Symantec Products - Symantec Altiris Notification Server Agent Privilege Escalation Vulnerability


February 6, 2008

Revision History



Remote AccessNo
Local AccessYes
Authentication RequiredYes
Exploit publicly availableNo


A privilege escalation vulnerability in the Symantec Altiris Notification Server Agent has been identified.

Affected Product(s)

Altiris Notification Server6.XAll6.0 SP3 R7


The Symantec Altiris Notification Server Agents are vulnerable to a shatter attack that can lead to privilege escalation. This attack is limited to users with login access to systems running the Symantec Altiris Notification Server Agent.

Symantec Response

Symantec engineers have verified and fixed this vulnerability. The following steps are required for remediation of this security issue:
Additional installation and configuration information can be found in KB Article 35803 at http://kb.altiris.com.

Best Practices

(this is for internal use only)
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 data base. The BID assigned is 27645 which can be found at http://www.securityfocus.com/bid/27645


Symantec would like to thank Brett Moore of Insomnia Security for reporting this issue and for 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: February 6, 2008
Security Response Blog
The State of Spam