What is the severity of CVE-2006-7038?

CVE-2006-7038 is classified as a high severity vulnerability due to its potential to cause denial of service.

How do I fix CVE-2006-7038?

To mitigate CVE-2006-7038, update MERCUR Messaging 2005 to Service Pack 4 or later.

What types of attacks can exploit CVE-2006-7038?

CVE-2006-7038 can be exploited through long command lines sent to port 32000 and malformed name service queries to the SMTP service.

Which versions of software are affected by CVE-2006-7038?

CVE-2006-7038 affects all versions of MERCUR Messaging 2005 before Service Pack 4, including 5.0 SP3.

Can CVE-2006-7038 cause permanent damage?

CVE-2006-7038 does not cause permanent damage but can lead to service disruption through crashes.

Vulnerability/
CVE-2006-7038

high

7.8

CWE

NVD-CWE-Other 119

23/2/2007

7/8/2024

CVE-2006-7038: Buffer Overflow

First published: Fri Feb 23 2007(Updated: )

Multiple buffer overflows in MERCUR Messaging 2005 before Service Pack 4 allow remote attackers to cause a denial of service (crash) via (1) "long command lines at port 32000" and (2) certain name service queries that are not properly handled by the SMTP service.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Atrium Software Mercur Messaging 2005	=5.0_sp3
Atrium Software Mercur Messaging 2005	=5.0_sp3
Atrium Software Mercur Messaging 2005	=5.0_sp3

Remedy

http://secunia.com/advisories/20432

Remedy

http://www.securityfocus.com/bid/18462

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2006-7038?
CVE-2006-7038 is classified as a high severity vulnerability due to its potential to cause denial of service.
How do I fix CVE-2006-7038?
To mitigate CVE-2006-7038, update MERCUR Messaging 2005 to Service Pack 4 or later.
What types of attacks can exploit CVE-2006-7038?
CVE-2006-7038 can be exploited through long command lines sent to port 32000 and malformed name service queries to the SMTP service.
Which versions of software are affected by CVE-2006-7038?
CVE-2006-7038 affects all versions of MERCUR Messaging 2005 before Service Pack 4, including 5.0 SP3.
Can CVE-2006-7038 cause permanent damage?
CVE-2006-7038 does not cause permanent damage but can lead to service disruption through crashes.

collector/nvd-historical
collector/nvd-index
agent/type
agent/softwarecombine
agent/remedy
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/weakness
agent/severity
agent/author
agent/references
agent/tags
agent/event
agent/first-publish-date
agent/description
agent/source
vendor/atrium software
canonical/atrium software mercur messaging 2005
version/atrium software mercur messaging 2005/5.0_sp3

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2006-7038?
CVE-2006-7038 is classified as a high severity vulnerability due to its potential to cause denial of service.
How do I fix CVE-2006-7038?
To mitigate CVE-2006-7038, update MERCUR Messaging 2005 to Service Pack 4 or later.
What types of attacks can exploit CVE-2006-7038?
CVE-2006-7038 can be exploited through long command lines sent to port 32000 and malformed name service queries to the SMTP service.
Which versions of software are affected by CVE-2006-7038?
CVE-2006-7038 affects all versions of MERCUR Messaging 2005 before Service Pack 4, including 5.0 SP3.
Can CVE-2006-7038 cause permanent damage?
CVE-2006-7038 does not cause permanent damage but can lead to service disruption through crashes.