dbcve.org
Odbc Driver For Sql ServerApplication · Microsoft

CVE-2024-28934

HIGH · 8.8 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 15.0.2110.4 / 15.0.4360.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A remote code execution vulnerability exists in the Microsoft ODBC Driver for SQL Server. An attacker who successfully exploits this vulnerability could execute arbitrary code on the target system. The vulnerability is rated high severity with CVSS 8.8, indicating it is remotely exploitable without authentication.

MitigationApply the security update provided by Microsoft for the ODBC Driver for SQL Server to all affected systems. Prioritize patching systems that have direct network exposure to the SQL Server endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Odbc Driver For Sql ServerApplication
Affected:>= 17.0.1.1, < 17.10.6.1>= 18.0.1.1, < 18.3.3.1
Sql Server 2019Application
Affected:>= 15.0.2000.5, < 15.0.2110.4>= 15.0.4003.23, < 15.0.4360.2
Sql Server 2022Application
Affected:>= 16.0.1000.6, < 16.0.1115.1>= 16.0.4003.1, < 16.0.4120.1
Visual Studio 2019Application
Affected:>= 16.0, < 16.11.35
Visual Studio 2022Application
Affected:>= 17.4.0, < 17.4.18>= 17.6.0, < 17.6.14>= 17.8.0, < 17.8.9>= 17.9.0, < 17.9.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check ODBC Driver for SQL Server version on Windows
    Open ODBC Data Sources (odbcad32.exe) or check the driver file version at C:\Windows\System32\msodbcsql*.dll, or query the registry under HKLM\SOFTWARE\ODBC\ODBCINST.INI\ODBC Driver for SQL Server
    Affected if The installed driver version is 17.x less than 17.10.6.1, or 18.x less than 18.3.3.1
  2. Check SQL Server 2019 instance version
    Run 'SELECT @@VERSION' via sqlcmd or SQL Server Management Studio, or check the registry under HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL15.MSSQLSERVER\CurrentVersion
    Affected if The build number is between 15.0.2000.5 and 15.0.2110.3 inclusive, or between 15.0.4003.23 and 15.0.4360.1 inclusive
  3. Check SQL Server 2022 instance version
    Run 'SELECT @@VERSION' via sqlcmd or SQL Server Management Studio, or check the registry under HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL16.MSSQLSERVER\CurrentVersion
    Affected if The build number is between 16.0.1000.6 and 16.0.1115.0 inclusive, or between 16.0.4003.1 and 16.0.4120.0 inclusive
  4. Check Visual Studio 2019 installation and version
    Open Visual Studio 2019, go to Help > About Microsoft Visual Studio, or check the registry under HKLM\SOFTWARE\Microsoft\VisualStudio\16.0\Version
    Affected if The version is 16.0 through 16.11.34 (any version below 16.11.35)
  5. Check Visual Studio 2022 installation and version
    Open Visual Studio 2022, go to Help > About Microsoft Visual Studio, or check the registry under HKLM\SOFTWARE\Microsoft\VisualStudio\17.0\Version
    Affected if The version falls in ranges 17.4.0-17.4.17, 17.6.0-17.6.13, 17.8.0-17.8.8, or 17.9.0-17.9.5

A system is affected if it has any ODBC Driver for SQL Server, SQL Server 2019/2022, or Visual Studio 2019/2022 installation with a version matching the affected ranges above.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 15.0.2110.4 / 15.0.4360.2 / 16.0.1115.1 or later
Fixed in 15.0.2110.415.0.4360.216.0.1115.1
Interim mitigation

Apply the security update provided by Microsoft for the ODBC Driver for SQL Server to all affected systems. Prioritize patching systems that have direct network exposure to the SQL Server endpoints.

Recommended fix High confidence

ODBC Driver 17.10.6.1 / 18.3.3.1; SQL Server 2019 15.0.2110.4 or 15.0.4360.2; SQL Server 2022 16.0.1115.1 or 16.0.4120.1; VS2019 16.11.35; VS2022 17.4.18/17.6.14/17.8.9/17.9.6

  1. For ODBC Driver for SQL Server: Upgrade to version 17.10.6.1 or later (for 17.x branch), or version 18.3.3.1 or later (for 18.x branch)
  2. For SQL Server 2019: Apply update version 15.0.2110.4 or later, or version 15.0.4360.2 or later
  3. For SQL Server 2022: Apply update version 16.0.1115.1 or later, or version 16.0.4120.1 or later
  4. For Visual Studio 2019: Update to version 16.11.35 or later
  5. For Visual Studio 2022: Update to version 17.4.18, 17.6.14, 17.8.9, or 17.9.6 or later respectively based on your current branch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Odbc Driver For Sql Server Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-28934 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-28934 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data