# CVE-2007-1578: Integer overflow in n/a

> Remote attackers can execute arbitrary code via a stack-based buffer overflow in the NTLM implementation of the MERCUR IMAPD server.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/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:** 21 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v8r8-w6r4-fw28

## What is CVE-2007-1578?

CVE-2007-1578 is a critical vulnerability in n/a, published on 21 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple integer signedness errors in the NTLM implementation in Atrium MERCUR IMAPD (mcrimap4.exe) 5.00.14, with SP4, allow remote attackers to execute arbitrary code via a long NTLMSSP argument that triggers a stack-based buffer overflow.

## Which versions are affected by CVE-2007-1578?

It affects 1 product.


Products: Atrium Software Mercur Imapd.

## How do I fix CVE-2007-1578?

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

## Is CVE-2007-1578 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-1578 exists.

Public exploit code:

- Mercur IMAPD 5.00.14 (Windows x86) - Remote Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-1579](https://insights.sbomify.com/CVE-2007-1579/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1578 and fix it if it is affected.

What it is: CVE-2007-1578 is a critical vulnerability in n/a, published on 21 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-1578 exists.

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-2007-1578/ (Markdown: https://insights.sbomify.com/CVE-2007-1578/index.md)
```

## Sources

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

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