1. Symantec/
  2. Security Response/
  3. Security Updates Detail

Security Advisories Relating to Symantec Products - Symantec Backup Exec Multiple Issues


August 1, 2013








Base Score



CVSS2 Vector

Linux Agent Utility Heap Overflow - High





Management Console/beutility XSS - Medium





Backup Data Storage Files Weak Permissions - Medium





NDMP Information Disclosure - Low







Symantec Backup Exec is susceptible to security issues including a remote heap overflow in the utility program shipping with the Linux agent. Also potentially susceptible to cross-site scripting (XSS) issues in the management console, unauthorized access to backup data due to weak permissions and an information disclosure in the NDMP protocol.  These issues could result in unauthorized OS version information disclosure, session hijacking/redirection or unauthorized access to sensitive information, crashing a Linux agent or potential elevation of privilege on a system hosting a Linux agent.

Product(s) Affected





Symantec Backup Exec



2012 SP2

Symantec Backup Exec

2010 R3


2010 R3 SP3



Symantec was notified of security issues in Symantec Backup Exec.  The utility program shipping with the Linux agent used to back-up MAC/Unix/Linux clients is susceptible to a heap overflow that could potentially result in crashing the agent or possibly allow unauthorized privilege access to the host.

During a normal backup process, backup and restore data files are stored with weak ACLs allowing r/w access to everyone.  This information could be useful to an authorized but non-privileged user able to access the stored data.  The information could be used to leverage unauthorized access to or elevated privilege on network systems.

The NMDP protocol shipped with Symantec Backup Exec leaks host versioning information that could provide reconnaissance information to a malicious authorized user.  The malicious user could potentially leverage this information for unauthorized access attempts against a network system.

The Symantec Backup Exec management console is susceptible to XSS issues in various pages used to generate custom reports, create Storage Devices and jobs. Beutility console is also susceptible to XSS issues when managing Backup Exec servers. A malicious user with authorized access to the management console or beutility could insert scripts that could be used to gather information from other authorized utility users potentially resulting in access to areas of the network or systems not normally authorized to them. 

In a normal Symantec Backup Exec installation, neither agents nor servers should be accessible outside of the network environment. These restrictions reduce exposure to these issues from external sources.  However, an external attacker able to successfully leverage network access or entice an authorized user to download a malicious code package could attempt to exploit some of these issues.

Symantec Response

Symantec engineers verified these issues and have released updates to address them. Customers should ensure they are on the latest release of Symantec Backup Exec 2012 or Symantec Backup Exec 2010 as indicated in the product matrix above.

Symantec is not aware of exploitation of or adverse customer impact from these issues.


Update Information

Updates are available through customers' normal support locations.

Best Practices

• As part of normal best practices, Symantec strongly recommends:

  • • Restrict access to administration or management systems to privileged users.
  • • Disable remote access if not required or restrict it to trusted/authorized systems only.
  • • Where possible, limit exposure of application and web interfaces to trusted/internal networks only.
  • • Keep all operating systems and applications updated with the latest vendor patches.
  • • Follow a multi-layered approach to security. Run both firewall and anti-malware applications, at a minimum, to provide multiple points of detection and protection to both inbound and outbound threats.
  • • Deploy network and host-based 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


Symantec thanks Perran Hill, Shaun Jones, Edward Torkington, Daniele Costa, and Andy Davis with NCC Group for discovering, reporting these issues and coordinating with us as we addressed them.


BID: Security Focus, http://www.securityfocus.com, has assigned Bugtraq IDs (BIDs) to these issues for inclusion in the Security Focus vulnerability database.

CVE: These issues are candidates for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems. 







BID 61485

Linux Agent Utility Heap Overflow


BID 61486

Management Console/beutility Console XSS


BID 61487

Backup Data Storage Files Weak Permissions


BID 61488

NDMP Information Disclosure



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 has developed a Software Security Vulnerability Management Process document outlining the process we follow in addressing suspected vulnerabilities in our products.
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 secure@symantec.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 secure@symantec.com.
The Symantec Software Security PGP key can be found at the following location:
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 secure@symantec.com.
Last modified on: August 1, 2013
Security Response Blog
The State of Spam