PatchTheCVEmercur messaging vulnerabilities and fixes
Recent CVEs affecting mercur messaging, with upgrade or downgrade steps. 3 tracked.
Also searched as: mercurmessaging.
mercur messaging has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2006-03-19. Highest priority: CVE-2006-1255 (score 65/100).
- CVE-2006-1255 HIGH 10.0 UPGRADE Stack-based buffer overflow in the IMAP service in Mercur Messaging 5.0 SP3 and earlier allows remote attacker
- CVE-2005-1657 HIGH 7.5 DOWNGRADE Multiple directory traversal vulnerabilities in Mercur Messaging 2005 SP2 allow remote attackers to perform un
- CVE-2005-1656 MEDIUM 5.0 DOWNGRADE Mercur Messaging 2005 SP2 allows remote attackers to read the source code of .ctml files via a URL with a trai
FAQ
How do I fix mercur messaging 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 being exploited right now?
None of the tracked mercur messaging CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which mercur messaging CVE should I patch first?
CVE-2006-1255 currently ranks highest (65/100): Stack-based buffer overflow in the IMAP service in Mercur Messaging 5.0 SP3 and earlier allows remote attacker.