Note: Customers running versions of Symantec SecurityExpressions Audit and Compliance Server prior to 4.1 should upgrade to the latest release and apply all available updates.
Symantec was notified of a cross-site scripting issue present in the Security Expression Audit and Compliance Server. The console fails to properly filter/ validate external client input from users with authorized access to the console. Error messages may be susceptible to unauthorized manipulation to generate potentially malicious scripts being directed to unsuspecting users.
Additionally, some response error messages are not properly encoded which could allow the potential for malicious HTML content to be injected into the returned response to a user. These issues could result in unauthorized access to other users’ sessions or to other systems on the internal network as well as unauthorized information disclosure.
Symantec product engineers have released a hot fix for these issues in affected product versions. Symantec recommends all customers apply the latest available update to protect against threats of this nature.
Symantec is not aware of any exploitation of or adverse customer impact from these issues.
Symantec recommends that all customers apply Hotfix 1 as described in Symantec KB Article 49452 to protect against potential attempts to exploit these issues. Symantec KB Article 49452 with Hotfix 1 for affected products is available from the following location: https://kb.altiris.com/article.asp?article=49452&p=1
If customers are unable to move to the latest release of Symantec SecurityExpressions Audit and Compliance Server or apply HotFix1 at this time, Symantec recommends ensuring console access is restricted to privileged users only until the upgrade can be applied.
As part of normal best practices, Symantec strongly recommends:
Restrict access to administration or management systems to privileged users.
Disable remote access or restrict it 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
Symantec would like to thank Nate Roberts with Wipfli, LLP for reporting these issues and coordinating with us while Symantec resolved them.
BID: Security Focus, http://www.securityfocus.com, has assigned a Bugtraq ID (BID) to these issues for inclusion in the Security Focus vulnerability database.
BID 36570 is assigned to the cross-site scripting issue
BID 36571 is assigned to the HTML Injection issue
CVE: These issues are candidates for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems. The CVE initiative has assigned
CVE-2009-3029 to the cross-site scripting issue
CVE-2009-3030 to the HTML Injection issue
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 firstname.lastname@example.org 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 email@example.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 firstname.lastname@example.org.