|Security Advisory ID SYMSA1153|
Initial Publication Date:
14 May 2008
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.
SeverityOne High severity issue
Five Medium severity issues
|Remote Access||Yes (authorized network access required)|
|Exploit publicly available||Yes, (for Sybsecurity reported issues)|
|Altiris Deployment Solution||6.8.x & 6.9.x||All builds prior to 6.9.176||6.9.176|
Details3Com Zero Day Initiative (ZDI) reported two issues:
- 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.
- 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.
- 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.
- 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
- 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.
- 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.
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 ResponseSymantec 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:
- Go to http://kb.altiris.com/
- 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.
Best PracticesAs 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
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.