Revision History None
Risk Impact Medium
|Remote Access (adjacent network)||Yes|
Overview A non-privileged but authorized user could potentially leverage Symantec Veritas NetBackup JAVA Administration Graphical User Interface (GUI) to execute code with elevated privileges on the server.
|Symantec Veritas NetBackup Enterprise Server and Symantec Veritas NetBackup Server||5.1||All||5.1 MP7|
Product versions prior to those listed above are NOT supported. Customers running legacy product versions should upgrade and apply available updates.
|Symantec Veritas NetBackup Enterprise Server and Symantec Veritas NetBackup Server||5.1 MP7||All|
Details The Java Administration GUI (jnbSA) in affected versions of Veritas NetBackup could potentially allow an authorized but non-privileged user to run commands which would normally require a higher privilege to execute. The malicious user would need to be authenticated on the system and logged in to the GUI in order to attempt to exploit this vulnerability.
Symantec engineers have verified that the vulnerability exists in the versions of Veritas NetBackup listed in the table above. Updates have been released to resolve the issue.
Symantec is not aware of any customers impacted by this issue, or of any attempts to exploit the issue.
The updates for affected products are available from the "Related Documents" section of the following Technote:
A successful attacker must be logged in to the GUI to launch an attack. Access to the NetBackup server should be limited to trusted users.
Customers who want to limit exposure to any possibility of this type of attempt prior to upgrading can disable the JAVA GUI as follows:
move the bpjava* binaries out of ’/usr/openv/netbackup/bin’ (UNIX/Linux)
out of ‘\VERITAS\Netbackup\bin’ (Windows)
As part of normal best practices, Symantec strongly recommends:
- Restrict access to administration or management systems to privileged users.
- Restrict remote access, if it is required, to trusted/authorized systems only.
- Run under the principle of least privilege where possible to limit the impact of potential exploits.
- 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
Credit Symantec would like to thank Kyle Noonan of Sun Microsystems for reporting this issue and coordinating with us on the resolution.
, has assigned BID 31221 to this issue
This issue is a candidate for inclusion in the CVE list (http://cve.mitre.org
), which standardizes names for security problems. 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.
REPORTING VULNERABILITIES TO SYMANTEC
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 responsible disclosure guidelines
Symantec Corporation firmly believes in a proactive approach to secure software development and implements security review into various stages of the software development process. Additionally, Symantec is committed to the security of its products and services as well as to its customers’ data. Symantec is committed to continually improving its software security process.
This document provides an overview of the current Secure Development Lifecycle (SDLC)
practice applicable to Symantec’s product and service teams as well as other software security related activities and policies used by such teams. This document is intended as a summary and does not represent a comprehensive list of security testing and practices conducted by Symantec in the software development process.
Please contact email@example.com
if you believe you have discovered a security issue in a Symantec product. A member of the Symantec Software Security team will contact you regarding your submission to coordinate any required response. Symantec strongly recommends using encrypted email for reporting vulnerability information to firstname.lastname@example.org
The Symantec Software Security PGP key can be found at the following location:
COPYRIGHT (C) 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 Software Security. Reprinting the whole or part of this alert in any medium other than electronically requires permission from email@example.com