# CVE-2005-0560: Memory corruption in n/a

> Remote attackers can execute arbitrary code on Exchange Server via a crafted SMTP request due to a heap-based buffer overflow.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/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:** 13 Apr 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hmrq-pv99-355p

## What is CVE-2005-0560?

CVE-2005-0560 is a high-severity memory corruption vulnerability in Microsoft Exchange Server, published on 13 Apr 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Heap-based buffer overflow in the SvrAppendReceivedChunk function in xlsasink.dll in the SMTP service of Exchange Server 2000 and 2003 allows remote attackers to execute arbitrary code via a crafted X-LINK2STATE extended verb request to the SMTP port.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2005-0560?

It affects 1 product.


Products: Microsoft Exchange Server.

## How do I fix CVE-2005-0560?

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

## Is CVE-2005-0560 being exploited?

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

Public exploit code:

- Microsoft Exchange Server - Remote Code Execution (MS05-021) (exploitdb)

## Other vulnerabilities in Microsoft Exchange Server

- [CVE-2024-21410](https://insights.sbomify.com/CVE-2024-21410/): Microsoft Exchange Server Privilege Escalation (critical 9.8, exploited in the wild)
- [CVE-2021-34473](https://insights.sbomify.com/CVE-2021-34473/): Microsoft Exchange Server Remote Code Execution (critical 9.1, exploited in the wild)
- [CVE-2021-26855](https://insights.sbomify.com/CVE-2021-26855/): Microsoft Exchange Server Remote Code Execution (critical 9.1, exploited in the wild)
- [CVE-2021-34523](https://insights.sbomify.com/CVE-2021-34523/): Microsoft Exchange Server Privilege Escalation (critical 9.0, exploited in the wild)
- [CVE-2023-21529](https://insights.sbomify.com/CVE-2023-21529/): Microsoft Exchange Server Deserialization of Untrusted Data (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0560 and fix it if it is affected.

What it is: CVE-2005-0560 is a high-severity memory corruption vulnerability in Microsoft Exchange Server, published on 13 Apr 2005. 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-2005-0560 exists.

Affected product: Microsoft Exchange Server. 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-2005-0560/ (Markdown: https://insights.sbomify.com/CVE-2005-0560/index.md)
```

## Sources

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

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