High (very configuration-dependent)
|Remote Access||network access or authorized user interaction required in normal configuration|
|Authentication Required||Authorized network access in normal configuration|
|Exploit publicly available||No|
A Heap Overflow vulnerability has been identified and resolved in the Veritas Enterprise Administrator (VEA) component, specifically in the administrative service. Symantecís VEA is the management GUI component of Veritas Storage Foundation. Successful exploitation of this issue can result in a crash of the service in both the 5.0 Windows and Unix versions. The potential for possible remote code execution in the 5.0 Windows version has been confirmed.
|Veritas Storage Foundation for Windows||5.0||Win2k, Win2003 32-bit||http://entsupport.symantec.com/docs/297166|
|Veritas Storage Foundation for Windows||5.0||Win2k, Win2003 64-bit||http://entsupport.symantec.com/docs/297167|
|Veritas Storage Foundation for Unix||5.0||Solaris, HP-UX, Linux, AIX||http://entsupport.symantec.com/docs/297464|
Note: Only those platforms and versions indicated are affected by this issue.
3Com ZDI notified Symantec of a heap overflow vulnerability identified in the Symantec VEA administrative service. The vulnerability was caused by a failure to properly validate incoming data passed to the administrative service resulting in a heap overflow. A specifically crafted packet passed to the vulnerable service could result in the administrative services terminating unexpectedly in the affected Windows and Unix versions. The potential to permit arbitrary code was verified in the affected Veritas Storage Foundation for Windows version. Successful exploitation could potentially result in a privileged-level compromise of the targeted system.
This vulnerability, if successfully exploited, would normally be the result of an internal attack by a malicious but authorized user or an individual who was able to leverage unauthorized access to a specific network segment. In Symantecís recommended installation the affected service should have limited or no exposure to the general internal network and no exposure outside of the corporate network as this greatly reduces the risk from unauthorized remote access through external, unauthenticated vectors.
Symantec takes the security of our products and our customers very seriously. Symantec engineers have verified and corrected these issues in all currently supported vulnerable versions of Symantecís Veritas Enterprise Administrator.
Updates are available for all supported products. Symantec recommends customers apply the latest product update available for their supported product versions to enhance their security posture and protect against potential security threats of this nature.
Symantec knows of no exploitation of or adverse customer impact from this issue.
Additional information concerning patches for affected products can be found at:
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.
Symantec credits Sebastian Apelt, email@example.com, working through 3Com ZDI for reporting this issue and for providing full coordination while Symantec resolved it.
The Common Vulnerabilities and Exposures (CVE) initiative has assigned CVE Candidate
CVE- 2008-0638 to this issue.
This issue is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems.
SecurityFocus has assigned BID 25778 to this vulnerability.
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 the principles of responsible disclosure. Symantec also subscribes to the vulnerability disclosure guidelines outlined by the National Infrastructure Advisory Council (NIAC).
Please contact firstname.lastname@example.org if you feel you have discovered a security issue in a Symantec product. A Symantec Product Security team member will contact you regarding your submission. Symantec strongly recommends using encrypted email for reporting vulnerability information to email@example.com. The Symantec Product Security PGP key can be found at the end of this message.
Symantec has developed a Product Vulnerability Response document outlining the process we follow in addressing suspected vulnerabilities in our products. This document is available below.
Copyright © 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 Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from firstname.lastname@example.org.
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and email@example.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.
Last modified on: Wednesday, 20-Feb-08 15:11:51