|Exploit publicly available||No|
An unauthorized script can be uploaded to Symantec Backup Exec System Recovery Manager.
|Symantec Backup Exec System Recovery Manager||7.0||7.0.3|
A flaw exists in the FileUpload Class running on the Symantec LiveState Apache Tomcat server. An unauthorized file can be uploaded to the server through a malicious HTTP Post and placed anywhere on the server. Remote code execution with System level access is possible.
Symantec has released an update for all affected versions of Symantec Backup Exec System Recovery Manager. The update can be downloaded from https://fileconnect.symantec.com.
The update should be installed over your current version of Backup Exec System Recovery Manager. This will create new Easy Installer packages for 7.03. Push out the new Backup Exec System Recovery 7.03/Management Control package to all machines. (This can be done either through email, SMS, Logon Script, or downloaded from each machine). The machine must be rebooted for the update to be available.
As part of normal best practices, Symantec strongly recommends:
- Restrict access to administration or management systems to privileged users.
- Restrict remote access, if required, to trusted/authorized systems only.
- Run under the principle of least privilege where possible to limit the impact of exploit by threats.
- 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
The Common Vulnerabilities and Exposures (CVE) initiative has assigned CVE Candidate numbers to this issue.
CVE Candidate CVE-2008-0457.
This issue is a candidate for inclusion in the CVE list (http://cve.mitre.org
), which standardizes names for security problems.
Symantec would like to acknowledge Titon of BastardLabs, working with 3COM/TippingPoint, and the Zero Day Initiative
, for reporting this 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 responsible disclosure guidelines
Please contact email@example.com
if you feel you have discovered a security issue in a Symantec product. A member of the Symantec Product 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 Product Security PGP key can be found at the location below.
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.
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 Product Security. Reprinting the whole or part of this alert in any medium other than electronically requires permission from email@example.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 Product Security, and firstname.lastname@example.org
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.