WelcomeEnterpriseSmall BusinessHome & Home OfficePartnersAbout Symantec
August 11, 2006
Symantec Backup Exec for Windows Server: RPC Interface Heap Overflow, Authorized User Potential Elevation of Privilege

Revision History


Authentication RequiredYes
Exploit publicly availableNo

The Backup Exec for Windows Server and Remote Agents for Window Server, also used by the Continuous Protection Server and Backup Exec for Netware Server, are vulnerable to heap overflows from specifically formatted internal network calls to RPC interfaces.

Affected Products
Backup Exec for Windows Server and Remote Agent9.19.1.4691HotFix Available
Backup Exec for Windows Server and Remote Agent10.010.0.5484HotFix Available
Backup Exec for Windows Server and Remote Agent10.010.0.5520HotFix Available
Backup Exec for Windows Server and Remote Agent10.110.1.5629HotFix Available
Backup Exec Continuous Protection Server Remote Agent for Windows Server10.110.1.325.6301HotFix Available
Backup Exec Continuous Protection Server Remote Agent for Windows Server10.110.1.326.1401HotFix Available
Backup Exec Continuous Protection Server Remote Agent for Windows Server10.110.1.326.2501HotFix Available
Backup Exec Continuous Protection Server Remote Agent for Windows Server10.110.1.326.3301HotFix Available
Backup Exec Continuous Protection Server Remote Agent for Windows Server10.110.1.327.401HotFix Available
Backup Exec for Netware Server Remote Agent for Windows Server9.1AllHotFix Available
Backup Exec for Netware Server Remote Agent for Windows Server9.2AllHotFix Available

Note: ONLY the products and versions listed above are affected by these issues.

Product versions prior to those listed above are NOT supported. Customers running legacy product versions should upgrade and apply available updates.

Tenable Network Security, notified Symantec of heap overflow issues they identified in the RPC interfaces of the Backup Exec for Window Servers and Remote Agents. The Remote Agent for Windows Server (RAWS) is also used by the Continuous Protection Server as well as Backup Exec for Netware Server depending on the customer's network environment. The overflows occur due to improper validation and subsequent handling of user input. Successful exploitation would require the attacker to have authorized but non-privileged access to the network on which the target system resides. A malicious user who attempted such an attack may cause the targeted application to crash but, if successfully exploited, could potentially execute arbitrary code and gain elevated privilege on the targeted system.

Symantec Response
Symantec engineers did an in-depth review of the reported issues and related file functionality to further enhance the overall security of Symantec Backup Exec for Windows Server and the Remote Agent for Windows Server and to resolve any additional potential concerns. Symantec engineers have addressed these issues in all currently supported versions of the products identified above. Security updates are available for all supported products.

Symantec strongly recommends all customers apply the latest security update as indicated for their supported product versions to protect against threats of this nature.

Symantec knows of no exploitation of or adverse customer impact from these issues.

The patches listed above for affected products are available from the following location:
http://support.veritas.com/docs/284343 for Symantec Backup Exec for Windows Server and Continuous Protection Server and http://support.veritas.com/docs/284623 for Backup Exec for Netware Server.

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

  • Restrict access to administration or management systems to authorized privileged users
  • 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

A CVE Candidate name has been requested from the Common Vulnerabilities and Exposures (CVE) initiative for this issue. This advisory will be revised accordingly upon receipt of the CVE Candidate name. This issue is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems.

Symantec thanks Nicolas Pouvesle from Tenable Network Security for reporting this finding and for excellent coordination while Symantec resolved the issue.

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: Friday, 11-Aug-06 06:15:00
Last modified on: Friday, 11-Aug-2006 06:45:34 PDT
[an error occurred while processing this directive]