# CVE-2008-5416: Memory corruption in n/a

> Remote authenticated users can execute arbitrary code or cause denial of service via a heap-based buffer overflow in SQL Server.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2008
- **Updated:** 7 Aug 2024
- **Also known as:** CVE-2008-4270, GHSA-qhrx-q7mr-q5x7

## What is CVE-2008-5416?

CVE-2008-5416 is a critical memory corruption vulnerability in Microsoft Sql Server, published on 10 Dec 2008. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Heap-based buffer overflow in Microsoft SQL Server 2000 SP4, 8.00.2050, 8.00.2039, and earlier; SQL Server 2000 Desktop Engine (MSDE 2000) SP4; SQL Server 2005 SP2 and 9.00.1399.06; SQL Server 2000 Desktop Engine (WMSDE) on Windows Server 2003 SP1 and SP2; and Windows Internal Database (WYukon) SP2 allows remote authenticated users to cause a denial of service (access violation exception) or execute arbitrary code by calling the sp_replwritetovarbin extended stored procedure with a set of invalid parameters that trigger memory overwrite, aka "SQL Server sp_replwritetovarbin Limited Memory Overwrite Vulnerability."

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2008-5416?

It affects 1 product.


Products: Microsoft Sql Server.

## How do I fix CVE-2008-5416?

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

## Is CVE-2008-5416 being exploited?

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

Public exploit code:

- Microsoft SQL Server sp_replwritetovarbin Memory Corruption via SQL Injection (github_poc): https://github.com/SECFORCE/CVE-2008-5416
- MS09-004 Microsoft SQL Server sp_replwritetovarbin Memory Corruption (metasploit)
- MS09-004 Microsoft SQL Server sp_replwritetovarbin Memory Corruption via SQL Injection (metasploit)
- Microsoft SQL Server - 'sp_replwritetovarbin()' Heap Overflow (exploitdb)
- Microsoft SQL Server - sp_replwritetovarbin Memory Corruption (MS09-004) (Metasploit) (exploitdb)
- Microsoft SQL Server - sp_replwritetovarbin Memory Corruption (MS09-004) (via SQL Injection) (Metasploit) (exploitdb)

## Other vulnerabilities in Microsoft Sql Server

- [CVE-2020-0618](https://insights.sbomify.com/CVE-2020-0618/): Microsoft SQL Server Reporting Services Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-1068](https://insights.sbomify.com/CVE-2019-1068/): Microsoft SQL Server Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2018-8273](https://insights.sbomify.com/CVE-2018-8273/): Memory corruption in Microsoft SQL Server (critical 9.8)
- [CVE-2023-21705](https://insights.sbomify.com/CVE-2023-21705/): Microsoft SQL Server Remote Code Execution Vulnerability (high 8.8)
- [CVE-2023-21713](https://insights.sbomify.com/CVE-2023-21713/): Microsoft SQL Server Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-5416 and fix it if it is affected.

What it is: CVE-2008-5416 is a critical memory corruption vulnerability in Microsoft Sql Server, published on 10 Dec 2008. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-5416 exists.

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

## Sources

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

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