WelcomeEnterpriseSmall BusinessHome & Home OfficePartnersAbout Symantec
November 28, 2006
Symantec NetBackup PureDisk: PHP update to Address Reported Security Vulnerability

Reference: http://www.securityfocus.com/bid/20879/

Revision History

High (configuration dependent)

Authentication RequiredYes (to network)
Exploit publicly availableNo

Symantec has released an update to address a security concern in PHP, a commonly used HTML-embedded scripting language, for Symantec's Veritas NetBackup 6.0 PureDisk Remote Office Edition. A heap overflow has been reported in the version of PHP shipped with the affected product builds listed below. The management interface of Symantec's product is accessible only through an SSL connection by default. Depending on configuration, however; an unauthorized user could potentially attempt to execute arbitrary code in the context of the vulnerable server, which runs in non-privileged mode by default.

Affected Products/Version
Symantec Veritas NetBackup PureDisk Remote Office Edition (all platforms)6.0GA, MP1NB_PDE_60_MP1_S01

Unaffected Products
Symantec Veritas NetBackup PureDisk Remote Office Edition (all platforms)6.1

Symantec Response
Symantec engineers have addressed the reported issue and provided Security updates. Symantec strongly recommends all customers apply the latest security update identified above or upgrade to Symantec Veritas NetBackup PureDisk Remote Office Edition 6.1 to protect against threats of this nature. Symantec knows of no exploitation of or adverse customer impact from this issue.

The patch is available from: http://support.veritas.com/docs/285984 for Symantec Veritas NetBackup PureDisk Remote Office Edition 6.0.

Best Practices
As part of normal best practices, Symantec recommends:

  • Restrict access to administration or management systems to authorized privileged users only
  • Block remote access to all ports not essential for efficient operation
  • Restrict remote access, if required, to trusted/authorized systems only
  • Remove/disable unnecessary accounts or restrict access according to security policy as required
  • Run under the principle of least privilege where possible
  • 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 latest vulnerabilities

CVE-2006-5465 has been assigned to this issue.

This issue is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems.

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 secure@symantec.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 secure@symantec.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.

PDF Symantec Vulnerability Response Policy PGP Symantec Product Vulnerability Management PGP Key

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 secure@symantec.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 secure@symantec.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.

Initial Post on: Tuesday, 28-Nov-06 14:05:00
Last modified on: Wednesday, 29-Nov-2006 11:25:51 PST
[an error occurred while processing this directive]