WelcomeEnterpriseSmall BusinessHome & Home OfficePartnersAbout Symantec
SYM05-009
May 31, 2005
Symantec Brightmail AntiSpam Static Database Password

Revision History
June 9, 2005 – updated version information

Risk Impact
Version dependent

Details
A static database administration password has been identified in Symantec’s Brightmail AnitiSpam product. This password could potentially allow remote administrative access to the database.

In product versions prior to Symantec Brightmail AntiSpam 6.0, the database is used to store quarantined SPAM for review. With the release of Symantec Brightmail AntiSpam version 6.0, some configuration information is now also stored in the database. The 6.0 release added security by restricting access to the admin account to localhost. However, Symantec engineers have found the restriction to localhost failed when upgrading from a prior version to Symantec Brightmail AntiSpam 6.0. It was only effective if a clean install of Symantec Brightmail AntiSpam 6.0 was done. Prior versions of Symantec Brightmail AntiSpam that were upgraded to 6.0 without doing a clean install remained remotely accessible.

Symantec Response
Symantec has released product update, 6.0.2, which properly addresses this issue. Symantec Brightmail AntiSpam 6.0.2 update includes the following:

1) The database root administrator account has been removed.
2) The installer for the brightmailuser account generates a random password.
3) The database account is restricted to localhost on all previously upgraded versions of the product

Affected Products

All Symantec Brightmail AntiSpam versions prior to 6.0 and those upgraded to 6.0 allow remote access to database administrator account. Database administrator access is limited to localhost for fresh installations of version 6.0.

Product Version Remote Database Access Configuration Data Access Risk
Brightmail AntiSpam upgraded to 6.0 or 6.0.1 from an earlier release Yes Yes High
Brightmail AntiSpam 6.0 Fresh Install No From localhost only (localhost only) Low
Brightmail AntiSpam 5.5 with Web Quarantine 1.0* Yes No Low

Note: Only Symantec products indicated above are potentially vulnerable. All other Symantec products are NOT affected.

Recommendations:
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 their product immediately to protect against these types of threats.

Updates are available through the Symantec Support site at http://www.symantec.com/techsupp.

Symantec is not aware of any active attempts against or organizations impacted by 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 secure@symantec.com 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 secure@symantec.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.

Symantec-Product-Vulnerability-Response Symantec Vulnerability Response Policy Symantec Product Vulnerability Management PGP Key Symantec Product Vulnerability Management PGP Key


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 secure@symantec.com.

Disclaimer
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 secure@symantec.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: Tuesday, 31-May-05 16:10:30
Last modified on: Thursday, 09-Jun-05 19:41:45