CVE-2006-7041
First published: Fri Feb 23 2007(Updated: )
The SMTP service in MERCUR Messaging 2005 before Service Pack 4 allows remote attackers to cause a denial of service (infinite loop) via a message in which neither the originator nor recipient address is known.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Mercur Mercur Messaging | =5.0_sp3 | |
| Mercur Mercur Messaging | =5.0_sp3 | |
| Mercur Mercur Messaging | =5.0_sp3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2006-7041?
CVE-2006-7041 is classified as a denial of service vulnerability.
How do I fix CVE-2006-7041?
To mitigate CVE-2006-7041, upgrade MERCUR Messaging 2005 to Service Pack 4 or later.
What types of attacks can exploit CVE-2006-7041?
CVE-2006-7041 can be exploited by sending specially crafted messages with unknown originator and recipient addresses.
Which versions of MERCUR Messaging are affected by CVE-2006-7041?
CVE-2006-7041 affects MERCUR Messaging 2005 versions prior to Service Pack 4.
What impact does CVE-2006-7041 have on my system?
Exploitation of CVE-2006-7041 can lead to an infinite loop, resulting in a denial of service.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/weakness
- agent/severity
- agent/author
- agent/references
- agent/event
- agent/first-publish-date
- agent/description
- agent/source
- agent/softwarecombine
- agent/tags
- collector/nvd-historical
- agent/software-canonical-lookup-request
- collector/nvd-index
- vendor/atrium software
- canonical/mercur mercur messaging
- version/mercur mercur messaging/5.0_sp3