Symantec Brightmail Anti-Spam Spamhunter denial of service
| symantec-brightmail-spamhunter-dos (18530) |  Low Risk |
Description:
Symantec Brightmail Anti-Spam is vulnerable to a denial of service attack, caused by a vulnerability in the Spamhunter module when converting headers to UTF. A remote attacker could use this vulnerability to cause the program to crash.
Platforms Affected:
- Microsoft, Windows 2003 Server
- RedHat, Enterprise Linux 3 AS
- RedHat, Enterprise Linux 3 ES
- Sun, Solaris 8
- Sun, Solaris 9
- Symantec, Brightmail AntiSpam 6.0.1
Remedy:
Apply patch 132 for this vulnerability, available from the Symantec FTP site. See References.
Consequences:
Denial of Service
References:
- Symantec FTP site, Patch 134 fixes a rare crash problem in Symantec[tm] Brightmail AntiSpam 6.0.1. at ftp://ftp.symantec.com/public/english_us_canada/products/sba/sba_60x/updates/p134_notes.htm.
- BID-12001: Symantec Brightmail Multiple Remote Denial of Service Vulnerabilities
- BID-12063: Symantec Brightmail AntiSpam Quarantine Multiple Remote Denial of Service Vulnerabilities
- CVE-2004-1768: The character converters in the Spamhunter and Language ID modules for Symantec Brightmail AntiSpam 6.0.1 before patch 132 allow remote attackers to cause a denial of service (crash) via messages with the ISO-8859-10 character set, which is not recognized by the converters.
- OSVDB ID: 12459: Symantec Brightmail AntiSpam Spamhunter module UTF Conversion DoS
- SA13489: Symantec Brightmail Denial of Service Vulnerabilities
- US-CERT VU#697598: Symantec Brightmail Anti-Spam Spamhunter UTF encoding error
Reported:
Dec 17, 2004
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