High (very configuration-dependent)
NOTE: In recommended installations, Symantec Veritas NetBackup systems should always be configured to be restricted to trusted-host access. The Veritas NetBackup Server and clients should never be exposed external to the network. The servers and clients could still be potentially susceptible to an insider-based attack however; this recommended configuration greatly reduces the risk from unauthorized remote access through external, unauthenticated vectors.
|Authentication Required||Yes, if properly configured to authenticate connecting hosts and/or only accept connections from trusted / authorized hosts|
|Exploit publicly available||No|
Multiple vulnerabilities have been identified in Symantec's Veritas NetBackup Master, Media Servers and clients. An attacker, able to access a vulnerable NetBackup host and successfully exploit these issues, could potentially cause execution of arbitrary code resulting in possible unauthorized, elevated access to the targeted system.
|NetBackup Enterprise Server/NetBackup Server; Server and client and Storage Migrator||6.0||All||All||6.0_MP4|
|NetBackup Enterprise Server/NetBackup Server; Server and client and Storage Migrator||5.1||All||All||5.1_MP6|
|NetBackup Enterprise Server/NetBackup Server; Server and client and Storage Migrator||5.0||All||All||5.0_MP7|
TippingPoint, a division of 3Com, notified Symantec of two buffer overflow vulnerabilities identified in the NetBackup bpcd daemon running on Symantec Veritas NetBackup Enterprise Servers and NetBackup Server and client systems as well as on Storage Migrator for Unix if that option is installed.
The overflows occur due to a failure to do proper input validation of incoming data. A remote attacker who successfully gains network access to an affected system and successfully passes a specifically crafted packet through one of the identified vectors to this vulnerable daemon could potentially execute arbitrary code with elevated privilege on the targeted system.
IBM Internet Security Systems notified Symantec of an additional programming logic error in how the bpcd daemon handles incoming system commands.
NetBackup fails to properly check the logic on incoming commands. A remote attacker who successfully gains access to the targeted system can append commands to a valid command and potentially leverage this issue to run arbitrary commands with elevated privilege on the targeted system.
Symantec takes the security of our products and our customers very seriously. Symantec engineers have verified and corrected these issues in all currently supported versions of NetBackup.
During a recent, focused, internal review of supported NetBackup product versions, Symantec engineers identified additional areas that could present potential security concerns. Symantec engineers were already in the process of preparing and testing updates for these issues and have accelerated relevant updates into the referenced Maintenance Pack releases to aid in addressing these issues.
Maintenance Pack updates are available for all supported products. The Maintenance Packs contain cumulative security-related fixes as well as additional product enhancements and technical updates. Symantec strongly recommends customers apply the latest Maintenance Pack releases 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 any of the issues noted in this advisory.
The patches listed above for affected products are available from the "Related Documents" section of the following Technote:
Implement NetBackup Access Control (NBAC) on NetBackup Servers and Clients
NBAC provides host-based authentication and user-level authorization through Veritas Security Services (VxSS) at both the server and the client to ensure communications are with a trusted host.
Implement Trusted-Host access through configuration files
Daemons associated with Veritas NetBackup services provide Trusted-Host access through the appropriate configuration files. Some of the services allow access by default while others deny access by default depending on the functionality of the service. Customers should follow the documentation provided for each service to ensure they have implemented a trusted-host relationship appropriate for their network.
The vmd, oprd and robotic daemons derive access control from the vm.conf file which allows access by default if there is no SERVER entry entered.
Using an appropriate text editor, configure vm.conf's "SERVER=<hostname>" for allowed host entries. Once a "SERVER=<hostname>" list is compiled, the associated daemons will ONLY trust and allow hosts annotated in vm.conf. Any malicious user or attacker would have to have either authorized access to or gain unauthorized access to one of the trusted-hosts to attempt attacks against a targeted server.
All other daemons associated with Veritas NetBackup derive access control from the NetBackup configuration which denies access by default.
Edit the configuration using "host properties" in the GUI to allow only those hosts that require access to associated NetBackup services. Any malicious user or attacker would have to have either authorized access to or gain unauthorized access to one of the trusted-hosts to attempt attacks against a targeted server.
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 such as this.
- Keep all operating systems and applications updated with the latest vendor patches.
- Follow a multi-layered approach to security. Run both firewall and antivirus applications, at a minimum, to provide multiple points of detection and protection to both inbound and outbound threats.
- Deploy network 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 these issues.
CVE Candidates CVE-2006-6222 and CVE-2006-5822 are assigned to the bpcd daemon buffer overflow issues identified by 3Com ZDI.
CVE Candidate CVE-2006-4902 is assigned to the bpcd daemon programming logic error identified by ISS.
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 Sebastian Apelt working with TippingPoint and the
Zero Day Initiative for reporting the issues referenced in CVE-2006-6222 and CVE-2006-5822 and providing full coordination while Symantec resolved them.
Symantec would also like to thank Paul Metha, a member of IBM Internet Security System's X-Force Research Team, for reporting the issue referenced in CVE-2006-4902 and 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 the principles of responsible disclosure. Symantec also subscribes to the vulnerability disclosure guidelines outlined by the National Infrastructure Advisory Council (NIAC).
Please contact email@example.com 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 firstname.lastname@example.org. 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 (c) 2009 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 email@example.com.
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 firstname.lastname@example.org 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.
Initial Post on: Wednesday, 13-Dec-06 12:05:00
Last modified on: Thursday, 14-Dec-06 15:30:14