# CVE-2024-28938: Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability

> A memory corruption vulnerability in the Microsoft ODBC Driver for SQL Server allows remote attackers to execute arbitrary code.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **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:** 9 Apr 2024
- **Updated:** 3 May 2025
- **Also known as:** GHSA-c37g-ppfr-pj55

## What is CVE-2024-28938?

CVE-2024-28938 is a high-severity memory corruption vulnerability in Microsoft Sql Server 2019, published on 9 Apr 2024. 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

Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2024-28938?

It affects 5 products.


Products: Microsoft Odbc Driver for Sql Server, Microsoft Sql Server 2019, Microsoft Sql Server 2022, Microsoft Visual Studio 2019, Microsoft Visual Studio 2022.

## How do I fix CVE-2024-28938?

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

## Is CVE-2024-28938 being exploited?

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

## Other vulnerabilities in Microsoft Sql Server 2019

- [CVE-2024-28929](https://insights.sbomify.com/CVE-2024-28929/): Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability (high 8.8)
- [CVE-2024-28930](https://insights.sbomify.com/CVE-2024-28930/): Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability (high 8.8)
- [CVE-2024-28931](https://insights.sbomify.com/CVE-2024-28931/): Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability (high 8.8)
- [CVE-2024-28932](https://insights.sbomify.com/CVE-2024-28932/): Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability (high 8.8)
- [CVE-2024-28933](https://insights.sbomify.com/CVE-2024-28933/): Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-28938 and fix it if it is affected.

What it is: CVE-2024-28938 is a high-severity memory corruption vulnerability in Microsoft Sql Server 2019, published on 9 Apr 2024. 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-2024-28938 exists.

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

## Sources

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

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