# CVE-2000-0198: Memory corruption in n/a

> Remote attackers can cause a denial of service in MERCUR mail server POP3 and IMAP services via a buffer overflow.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Mar 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-q5px-r484-x44m

## What is CVE-2000-0198?

CVE-2000-0198 is a medium-severity memory corruption vulnerability in n/a, published on 22 Mar 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in POP3 and IMAP servers in the MERCUR mail server suite allows remote attackers to cause a denial of service.

## Which versions are affected by CVE-2000-0198?

It affects 3 products.


Products: Atrium Software Mercur Imap4 Server, Atrium Software Mercur Mailserver, Atrium Software Mercur Pop3 Server.

## How do I fix CVE-2000-0198?

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

## Is CVE-2000-0198 being exploited?

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

Public exploit code:

- Atrium Software Mercur Mail Server 3.2 - Multiple Buffer Overflows (1) (exploitdb)
- Atrium Software Mercur Mail Server 3.2 - Multiple Buffer Overflows (2) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2000-0239](https://insights.sbomify.com/CVE-2000-0239/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0198 and fix it if it is affected.

What it is: CVE-2000-0198 is a medium-severity memory corruption vulnerability in n/a, published on 22 Mar 2000. 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-2000-0198 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-2000-0198/ (Markdown: https://insights.sbomify.com/CVE-2000-0198/index.md)
```

## Sources

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

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