mercur messaging 2005 vulnerabilities and fixes
Recent CVEs affecting mercur messaging 2005, with upgrade or downgrade steps. 5 tracked.
Also searched as: mercurmessaging2005.
mercur messaging 2005 has 5 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2007-03-21. Highest priority: CVE-2007-1579 (score 65/100).
- CVE-2007-1579 HIGH 10.0 MITIGATE DOWNGRADE Stack-based buffer overflow in Atrium MERCUR IMAPD allows remote attackers to have an unknown impact via a cer
- CVE-2006-7041 HIGH 7.8 DOWNGRADE The SMTP service in MERCUR Messaging 2005 before Service Pack 4 allows remote attackers to cause a denial of s
- CVE-2006-7040 HIGH 7.8 DOWNGRADE Unspecified vulnerability in MERCUR Messaging 2005 before Service Pack 4 allows remote attackers to cause a de
- CVE-2006-7039 MEDIUM 5.0 DOWNGRADE The IMAP4 service in MERCUR Messaging 2005 before Service Pack 4 allows remote attackers to cause a denial of
- CVE-2006-7038 HIGH 7.8 DOWNGRADE Multiple buffer overflows in MERCUR Messaging 2005 before Service Pack 4 allow remote attackers to cause a den
FAQ
How do I fix mercur messaging 2005 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 mercur messaging 2005 being exploited right now?
None of the tracked mercur messaging 2005 CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which mercur messaging 2005 CVE should I patch first?
CVE-2007-1579 currently ranks highest (65/100): Stack-based buffer overflow in Atrium MERCUR IMAPD allows remote attackers to have an unknown impact via a cer.