dbcve.org
Ole Db Driver For Sql ServerApplication · Microsoft

CVE-2024-28914

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 OLE DB 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

Microsoft OLE DB Driver for SQL Server contains a remote code execution vulnerability. The vulnerability likely exists in how the driver processes responses from SQL Server, potentially allowing an attacker who controls the database server or can inject malicious data to execute arbitrary code on connected client systems.

MitigationApply Microsoft security updates for the OLE DB Driver for SQL Server immediately. Ensure all systems using this driver are patched to the latest version.

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
Ole Db Driver For Sql ServerApplication
Affected:>= 18.0.2, < 18.7.0002.0>= 19.0.0, < 19.3.0003.0
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

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 OLE DB Driver for SQL Server version
    Open PowerShell and run: Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Microsoft SQL Server\MSOLEDBSQL\CurrentVersion' | Select-Object ProductVersion, Version
    Affected if The installed version is 18.0.2 or higher but below 18.7.0002.0, OR 19.0.0 or higher but below 19.3.0003.0
  2. Check SQL Server 2019 version
    Open SQL Server Management Studio or run: SELECT @@VERSION in a SQL query, or check registry key HKLM:\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL15.InstanceName\CurrentVersion
    Affected if The installed version is 15.0.2000.5 or higher but below 15.0.2110.4, OR 15.0.4003.23 or higher but below 15.0.4360.2
  3. Check SQL Server 2022 version
    Open SQL Server Management Studio or run: SELECT @@VERSION in a SQL query, or check registry key HKLM:\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL16.InstanceName\CurrentVersion
    Affected if The installed version is 16.0.1000.6 or higher but below 16.0.1115.1, OR 16.0.4003.1 or higher but below 16.0.4120.1
  4. Verify if OLE DB provider is in use
    Check application connection strings for 'Provider=MSOLEDBSQL' or review SQL Server error logs and trace flags related to OLE DB connections
    Affected if Applications use MSOLEDBSQL provider to connect to affected SQL Server instances

A system is affected if it runs any version of OLE DB Driver for SQL Server 18.x before 18.7.0002.0 or 19.x before 19.3.0003.0, OR runs SQL Server 2019 or 2022 in the affected version ranges and accepts connections from OLE DB clients.

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 Microsoft security updates for the OLE DB Driver for SQL Server immediately. Ensure all systems using this driver are patched to the latest version.

Recommended fix High confidence

Ole DB Driver 18.x to 18.7.0002.0+, Ole DB Driver 19.x to 19.3.0003.0+; SQL Server 2019 to CU24 (15.0.4360.2+); SQL Server 2022 to CU12 (16.0.4120.1+)

  1. Identify which Ole DB Driver for SQL Server version is in use by checking the installed version of msoledbsql.dll or the NuGet package version
  2. For standalone Ole DB Driver: download and install Microsoft OLE DB Driver for SQL Server version 18.7.0002.0 or later, or version 19.3.0003.0 or later
  3. For SQL Server 2019: apply SQL Server 2019 cumulative update 24 (version 15.0.4360.2 or later) or if on newer branch, update to 15.0.4360.2 or later
  4. For SQL Server 2022: apply SQL Server 2022 cumulative update 12 (version 16.0.4120.1 or later) or if on newer branch, update to 16.0.4120.1 or later
  5. Test the update in a non-production environment before deploying to production
  6. Restart affected services or applications that use the OLE DB connection after the update
Caveat Review release notes for any breaking changes in the cumulative updates; test application compatibility with the new driver version before production deployment

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

Fix this in Ole Db Driver For Sql Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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