|Exploit publicly available||No|
The administrator password for Symantec Reporting Server could be disclosed after a failed login attempt.
|Product||Affected Version||Updated Version||Solution|
SAV 10.1 MR6 build 6000 (10.1.6.6000) or later
SCS 3.1 MR6 build 6000 (188.8.131.5200) or later
Symantec Reporting Server is distributed with Symantec AntiVirus Corporate Edition 10.1 and later and Symantec Client Security 3.1 and later. The first publicly available version of Reporting Server was 184.108.40.206. All builds of Reporting prior to the Updated version listed above are impacted by this vulnerability.
Norton product line
Symantec Reporting Server is an optional web application within the Symantec System Center console that can be used to create reports about Symantec Client Security and Symantec AntiVirus products in an enterprise network. Symantec was notified that a failed attempt to log in to the Reporting Server could result in displaying a hashed version of the password. An attacker could potentially use the hashed password to gain access to the Reporting Server database with administrator rights.
Symantec engineers confirmed that this vulnerability exists in the versions of Reporting Server included with Symantec Client Security 3.1 and SAV CE 10.1, as indicated in the table above. Updates have been released to address the vulnerability.
A successful attacker would gain access only to the Reporting Server database. The attacker would not automatically have access to other programs on the computer, unless the same account and password are used for other programs. As a best practice, the accounts created for managing Reporting Server should not use the same id and password as the users’ network login credentials.
During the internal review of the issue, Symantec engineers also identified and fixed a separate issue which could allow an attacker to disable the authentication system for the SCS Reporting Server. If successfully exploited, this could allow a remote attacker to bypass authentication and access the reporting database.
Updates for both issues are included in SAV CE and SCS builds indicated in the Solution field of the Affected Products table above.
- Uninstall Reporting Server if it is not being used
- Symantec Client Security Console and the Reporting Server interface should be restricted to trusted access only.
- Ensuring that the Console is never visible external to the network greatly reduces opportunities for unauthorized remote access.
- User accounts for Reporting Server should be different than the user's network login account.
Applying the Updates
Reporting Server is an optional component of Symantec Client Security, and it can be updated (migrated) independently of the rest of the program. For more information, please see this knowledgebase document:
Migrating Reporting Server for Symantec Client Security 3.1 and Symantec AntiVirus 10.1
Symantec is not aware of any customers impacted by this issue, or of any attempts to exploit the issue.
As a part of normal best practices, users should keep vendor-supplied patches for all application software and operating systems up-to-date. Symantec strongly recommends any affected customers update Reporting Server immediately to protect against possible attempts to exploit this vulnerability.
Symantec would like to thank Mikko Korppi for reporting this issue, and coordinating with us on the response.
This issue is a candidate for inclusion in the Common Vulnerabilities and Exposures (CVE) list (http://cve.mitre.org), which standardizes names for security problems. The CVE initiative has assigned CVE-2007-3022 to 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 the principles of responsible disclosure. Symantec also subscribes to the vulnerability disclosure guidelines outlined by the National Infrastructure Advisory Council (NIAC).
Please contact firstname.lastname@example.org if you feel you have discovered a security issue in a Symantec product. A Symantec Product Security team member will contact you regarding your submission. Symantec strongly recommends using encrypted email for reporting vulnerability information to email@example.com. The Symantec Product Security PGP key can be found at the end of this message.
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) 2009 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 Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from firstname.lastname@example.org.
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 Security Response, and email@example.com 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.
Initial Post on: Friday, 01-Jun-07 13:00:00
Last modified on: Monday, 18-Jun-07 19:34:45