Odbc Driver For Sql ServerApplication · Microsoft

CVE-2024-28930

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

NVD · unedited

Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability

Technical summary

dbcve analysis · moderate confidence

This is a Remote Code Execution vulnerability in the Microsoft ODBC Driver for SQL Server. The ODBC driver contains a vulnerability that could allow an attacker to execute arbitrary code on the target system, likely through specially crafted SQL queries or connection attempts.

MitigationApply Microsoft security updates for the ODBC Driver for SQL Server promptly. Ensure the driver is updated to the latest patched version.

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

Affected products & versions

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

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?

dbcve checks

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

Identify installed ODBC Driver for SQL Server version

Open PowerShell and run: (Get-ItemProperty -Path 'HKLM:\SOFTWARE\ODBC\ODBCINST.INI\ODBC Driver 17 for SQL Server' -ErrorAction SilentlyContinue).Version. Also check for ODBC Driver 18. Run multiple queries if needed for different driver numbers.

Affected if Version is 17.x between 17.0.1.1 and 17.10.6.1 (exclusive of 17.10.6.1), or 18.x between 18.0.1.1 and 18.3.3.1 (exclusive of 18.3.3.1)
Identify SQL Server 2019 version

Open SQL Server Management Studio, right-click the server instance, select Properties, and note the version number displayed. Alternatively, run 'SELECT @@VERSION' in a new query.

Affected if Version starts with 15.0.2000.5 through 15.0.2110.4, or 15.0.4003.23 through 15.0.4360.2 (any build between these ranges)
Identify SQL Server 2022 version

Open SQL Server Management Studio, right-click the server instance, select Properties. Alternatively, run 'SELECT @@VERSION' in a new query.

Affected if Version starts with 16.0.1000.6 through 16.0.1115.1, or 16.0.4003.1 through 16.0.4120.1 (any build between these ranges)
Identify Visual Studio 2019 version

Open Visual Studio Installer, click on the Visual Studio 2019 tile, and note the version shown below the product name. Or check registry: HKLM\SOFTWARE\Microsoft\VisualStudio\16.0\Version

Affected if Version is 16.0.x where x is any build less than 16.11.35, or the version shows 16.1 through 16.10 range that is below 16.11.35
Identify Visual Studio 2022 version

Open Visual Studio Installer, click on the Visual Studio 2022 tile, and note the version. Or check registry: HKLM\SOFTWARE\Microsoft\VisualStudio\17.0\Version

Affected if Version is 17.4.x (below 17.4.18), 17.6.x (below 17.6.14), 17.8.x (below 17.8.9), or 17.9.x (below 17.9.6)

You are affected if any installed ODBC Driver for SQL Server, SQL Server 2019/2022, or Visual Studio 2019/2022 version falls within the specific version ranges listed for this CVE.

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

Remediation

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 Microsoft security updates for the ODBC Driver for SQL Server promptly. Ensure the driver is updated to the latest patched version.

Recommended fix High confidence

ODBC Driver 17.10.6.1/18.3.3.1; SQL Server 2019 CU21/CU32; SQL Server 2022 CU6/CU13; VS2019 16.11.35; VS2022 17.4.18/17.6.14/17.8.9/17.9.6

1. Identify which Microsoft products using ODBC Driver for SQL Server are deployed in your environment
2. For ODBC Driver for SQL Server: upgrade to version 17.10.6.1 or 18.3.3.1 (or newer)
3. For SQL Server 2019: apply Cumulative Update 21 (version 15.0.2110.4) or Cumulative Update 32 (version 15.0.4360.2)
4. For SQL Server 2022: apply Cumulative Update 6 (version 16.0.1115.1) or Cumulative Update 13 (version 16.0.4120.1)
5. For Visual Studio 2019: update to version 16.11.35
6. For Visual Studio 2022: update to version 17.4.18, 17.6.14, 17.8.9, or 17.9.6 depending on your current minor version
7. Test the updated components in a non-production environment before deploying to production

Caveat These are cumulative security updates with minimal breaking change risk; however, test thoroughly in non-production first

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

Consultation4.0 h
Implementation8.0 h
Testing6.0 h
Review / QA2.0 h

20.0 hours of engineering $3,500

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2024-28930 — 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

Primary sources

msrc.microsoft.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2024-28930?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 15.0.2110.4 / 15.0.4360.2 or later

Severity 8.8 High

Exploit likelihood EPSS, next 30 days 2.4%

Affects: Odbc Driver For Sql Server

Remediation

A high-priority fix

Fix this in Odbc Driver For Sql Server 20 hrs · Moderate

Typical engagement from $3,500

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2024-28930 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References