search menu icon-carat-right cmu-wordmark

CERT Coordination Center

Symantec VERITAS NetBackup Catalog daemon buffer overflow

Vulnerability Note VU#744137

Original Release Date: 2006-03-29 | Last Revised: 2006-03-29

Overview

The NetBackup Catalog daemon contains a stack-based buffer overflow that could allow a remote attacker to execute arbitrary code on a NetBackup master server.

Description

VERITAS NetBackup

Netbackup is a data backup and recovery solution with support for "over the network" backup.

NetBackup Catalog daemon (bpdbm)

The NetBackup Catalog daemon handles queries against internal NetBackup databases, known as catalogs. This daemon is also referred to as the NetBackup Database Manager.

The problem

The NetBackup Catalog daemon contains a stack-based buffer overflow. The problem is due to a lack of bounds checking on a buffer used to hold user-controlled data. The buffer overflow can be triggered by sending a specially crafted packet to a vulnerable NetBackup master server. More information is available in Symantec Security Advisory SYM06-006.

Considerations

The NetBackup Catalog daemon only runs on NetBackup master servers.

Impact

By sending a specially crafted packet to a vulnerable Netbackup master a remote, unauthenticated attacker may be able to execute arbitrary code with the privileges of the NetBackup Catalog daemon, typically root.

Solution

Apply patches from Symantec/VERITAS
Symantec/VERITAS has released patches to correct this issue in Symantec Security Advisory SYM06-006.

Restrict access

You may wish to block access to the vulnerable software from outside your network perimeter, specifically by blocking access to the ports used by NetBackup Catalog daemon (typically 13721/tcp). This will limit your exposure to attacks. However, blocking at the network perimeter would still allow attackers within the perimeter of your network to exploit the vulnerability. The use of host-based firewalls in addition to network-based firewalls can help restrict access to specific hosts within the network. It is important to understand your network's configuration and service requirements before deciding what changes are appropriate.


Note: even if patching can be done quickly, the above workaround measures should be considered as part of a defense-in-depth strategy for protecting your systems.

Vendor Information

744137
 

Symantec, Inc. Affected

Updated:  March 29, 2006

Status

Affected

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

See http://support.veritas.com/docs/281521 and http://securityresponse.symantec.com/avcenter/security/Content/2006.03.27.html.

If you have feedback, comments, or additional information about this vulnerability, please send us email.

Veritas, Inc. Affected

Updated:  March 29, 2006

Status

Affected

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

See http://support.veritas.com/docs/281521 and http://securityresponse.symantec.com/avcenter/security/Content/2006.03.27.html.

If you have feedback, comments, or additional information about this vulnerability, please send us email.


CVSS Metrics

Group Score Vector
Base
Temporal
Environmental

References

Acknowledgements

This vulnerability was reported by TippingPoint Security Research.

This document was written by Jeff Gennari.

Other Information

CVE IDs: CVE-2006-0990
Severity Metric: 22.05
Date Public: 2006-03-27
Date First Published: 2006-03-29
Date Last Updated: 2006-03-29 21:21 UTC
Document Revision: 29

Sponsored by CISA.