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

> Remote attackers can execute arbitrary code via a buffer overflow in email headers, requiring user interaction to open the malicious email.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Oct 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-4w6m-4639-4jgr

## What is CVE-2000-0567?

CVE-2000-0567 is a medium-severity memory corruption vulnerability in Microsoft Outlook, published on 13 Oct 2000. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in Microsoft Outlook and Outlook Express allows remote attackers to execute arbitrary commands via a long Date field in an email header, aka the "Malformed E-mail Header" vulnerability.

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

It affects 2 products.


Products: Microsoft Outlook, Microsoft Outlook Express.

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

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

## Is CVE-2000-0567 being exploited?

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

Public exploit code:

- Microsoft Outlook 97/98/2000 / Outlook Express 4.0/5.0 - GMT Field Buffer Overflow (1) (exploitdb)
- Microsoft Outlook 97/98/2000 / Outlook Express 4.0/5.0 - GMT Field Buffer Overflow (2) (exploitdb)

## Other vulnerabilities in Microsoft Outlook

- [CVE-2017-11774](https://insights.sbomify.com/CVE-2017-11774/): Microsoft Office Outlook Security Feature Bypass (high 7.8, exploited in the wild)
- [CVE-2001-0538](https://insights.sbomify.com/CVE-2001-0538/): Code injection in n/a (critical 10.0)
- [CVE-2013-3870](https://insights.sbomify.com/CVE-2013-3870/): Use after free in n/a (critical 9.3)
- [CVE-2010-2728](https://insights.sbomify.com/CVE-2010-2728/): Memory corruption in n/a (critical 9.3)
- [CVE-2010-0266](https://insights.sbomify.com/CVE-2010-0266/): Code injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2000-0567 is a medium-severity memory corruption vulnerability in Microsoft Outlook, published on 13 Oct 2000. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-0567 exists.

Affected product: Microsoft Outlook. 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-0567/ (Markdown: https://insights.sbomify.com/CVE-2000-0567/index.md)
```

## Sources

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

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