mailsweeper for smtp vulnerabilities and fixes
Recent CVEs affecting mailsweeper for smtp, with upgrade or downgrade steps. 5 tracked.
Also searched as: mailsweeperforsmtp.
mailsweeper for smtp has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2006-06-24. Highest priority: CVE-2006-3215 (score 46/100).
- CVE-2000-0932 MEDIUM 5.0 DOWNGRADE MAILsweeper for SMTP 3.x does not properly handle corrupt CDA documents in a ZIP file and hangs, which allows
- CVE-2006-3216 MEDIUM 5.0 UPGRADE UPGRADE Clearswift MAILsweeper for SMTP before 4.3.20 and MAILsweeper for Exchange before 4.3.20 allows remote attacke
- CVE-2006-3215 HIGH 7.5 UPGRADE UPGRADE Clearswift MAILsweeper for SMTP before 4.3.20 and MAILsweeper for Exchange before 4.3.20 allows remote attacke
- CVE-2004-2703 MEDIUM 4.3 MITIGATE MITIGATE Clearswift MIMEsweeper 5.0.5, when it has been upgraded from MAILsweeper for SMTP version 4.3 or MAILsweeper B
- CVE-2003-1477 HIGH 7.8 DOWNGRADE MAILsweeper for SMTP 4.3.6 and 4.3.7 allows remote attackers to cause a denial of service (CPU consumption) vi
FAQ
How do I fix mailsweeper for smtp vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is mailsweeper for smtp being exploited right now?
None of the tracked mailsweeper for smtp CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which mailsweeper for smtp CVE should I patch first?
CVE-2006-3215 currently ranks highest (46/100): Clearswift MAILsweeper for SMTP before 4.3.20 and MAILsweeper for Exchange before 4.3.20 allows remote attacke.