# CVE-2006-7038: Memory corruption in n/a

> Remote attackers can crash MERCUR Messaging via buffer overflows in command lines or SMTP queries, requiring a service pack update.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mh3j-qxmv-rf26

## What is CVE-2006-7038?

CVE-2006-7038 is a high-severity memory corruption vulnerability in n/a, published on 23 Feb 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2006-7038?

It affects 1 product.


Products: Atrium Software Mercur Messaging 2005.

## How do I fix CVE-2006-7038?

No fix has been published for CVE-2006-7038 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-7038 being exploited?

There is no known exploitation of CVE-2006-7038 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2006-7040](https://insights.sbomify.com/CVE-2006-7040/): Denial of service in n/a (high 7.8)
- [CVE-2006-7041](https://insights.sbomify.com/CVE-2006-7041/): Denial of service in n/a (high 7.8)
- [CVE-2006-7039](https://insights.sbomify.com/CVE-2006-7039/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-7038 and fix it if it is affected.

What it is: CVE-2006-7038 is a high-severity memory corruption vulnerability in n/a, published on 23 Feb 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-7038 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2006-7038/ (Markdown: https://insights.sbomify.com/CVE-2006-7038/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-7038
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-7038
- OSV: https://osv.dev/vulnerability/CVE-2006-7038

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-7038/
Summaries are generated and may contain mistakes; the official description above is the record.