Symantec Brightmail static database password security bypass
| brightmail-static-database-security-bypass (20804) |  High Risk |
Description:
Symantec Brightmail Anti-Spam could allow a remote attacker to bypass security restrictions caused by a vulnerability with a static database administration password. A remote attacker could use this vulnerability to bypass security and gain administrative access to the database that contains the quarantined messages for review including specific configuration information.
Consequences:
Bypass Security
Remedy:
Upgrade to the latest version of Symantec Brightmail (6.0.2 or later), as listed in Symantec LiveUpdate, as listed in Symantec Security Response SYM05-009. See References.
References:
- Symantec Brightmail AntiSpam Web page: Symantec Brightmail AntiSpam.
- Symantec Security Response SYM05-009: Symantec Brightmail AntiSpam Static Database Password.
- BID-13828: Symantec Brightmail AntiSpam Remote Information Disclosure Vulnerability
- CVE-2005-1867: Symantec Brightmail AntiSpam before 6.0.2 has a hard-coded database administrator password, which allows remote attackers to gain privileges.
- SA15562: Symantec Brightmail AntiSpam Static Database Password
- SECTRACK ID: 1014088: Symantec Brightmail AntiSpam Uses Common Default Database Password
- VUPEN/ADV-2005-0671: Symantec Brightmail AntiSpam Static Database Password Issue
Platforms Affected:
- Microsoft Windows 2003 Server
- Symantec Brightmail AntiSpam 4.0
- Symantec Brightmail AntiSpam 5.5
- Symantec Brightmail AntiSpam 6.0
- Symantec Brightmail AntiSpam 6.0.1
Reported:
Jun 01, 2005
The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.
For corrections or additions please email xforce@iss.net