CVE-2004-1768 symantec brightmail antispam
symantec brightmail antispam: no CVSS score yet. EPSS 2.1% estimated probability of exploitation activity in the next 30 days.
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.
- EPSS
- 2.1% (unchanged from 2.1% a week ago; 2.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 82nd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Fix and patched versions
- Patch: ftp://ftp.symantec.com/public/english_us_canada/products/sba/sba_60x/updates/p132_notes.htm
- Patch: http://secunia.com/advisories/13489
- Patch: http://www.kb.cert.org/vuls/id/697598
- Vendor advisory: http://secunia.com/advisories/13489
- Vendor advisory: http://www.osvdb.org/12459
Ask an AI about this CVE
Show the prompt
Explain CVE-2004-1768 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2004-1768?via=ask-ai-copy and https://cve.bz/cve/CVE-2004-1768?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2004-1768 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| symantec:brightmail_antispam | 6.0.1 |