Revision History None
|Exploit publicly available||No|
Overview Symantec’s Ghost Solution Suite fails to verify authenticity during communications.
|Symantec Ghost Solution Suite||1.1||1.1 patch 2|
|Symantec Ghost Solution Suite||2.0.0, 2.0.1||2.0.2|
Details Symantec’s Ghost Solution Suite’s does not authenticate network connections between the Ghost console and the Ghost Management Agent. By using ARP Spoofing, an attacker could possibly impersonate the Symantec Ghost Solution Suite server and execute commands on the client with SYSTEM privileges. However in order to exploit this weakness, an attacker would have to have authorized access to the internal network and have a working knowledge of the Ghost client-server RPC. NOTE: customers who do not use the Ghost Console or the Ghost Management Agent are not vulnerable to this exploit.
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
The Common Vulnerabilities and Exposures (CVE) initiative has assigned CVE Candidate numbers to this issue.
CVE Candidate CVE-2008-0640
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 Nicolas Pouvesle with the Tenable Security
for reporting this issue.
REPORTING VULNERABILITIES TO SYMANTEC
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 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 firstname.lastname@example.org
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 email@example.com
The Symantec Software Security PGP key can be found at the following location:
COPYRIGHT (C) BY SYMANTEC CORP.
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 firstname.lastname@example.org