dbcve.org
Ole Db Driver For Sql ServerApplication · Microsoft

CVE-2024-28909

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

A remote code execution vulnerability exists in Microsoft OLE DB Driver for SQL Server that could allow an attacker to execute arbitrary code on affected systems. The vulnerability stems from improper handling of specific inputs or operations within the OLE DB driver component.

MitigationApply Microsoft security updates for the OLE DB Driver for SQL Server as soon as they become available, or upgrade to patched versions. Prioritize affected SQL Server and dependent applications in the deployment environment.

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 or Command Prompt and run: 'msiexec /q /i' on the installed MSI, or check the file version of 'oledb32.dll' in the SQL Server installation directory (typically C:\Program Files\Microsoft OLE DB Driver for SQL Server\bin\). You can also check via Registry: HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\OLEDB\CurrentVersion
    Affected if Version is 18.0.2 through 18.7.0001.x, or 19.0.0 through 19.3.0002.x (i.e., >= 18.0.2 and < 18.7.0002.0, or >= 19.0.0 and < 19.3.0003.0)
  2. Check SQL Server 2019 version
    Open SQL Server Configuration Manager or run 'SELECT @@VERSION' in SQL Server Management Studio, or check the SQL Server version via Registry under HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL15.InstanceName\CurrentVersion
    Affected if Version is 15.0.2000.5 through 15.0.2110.3, or 15.0.4003.23 through 15.0.4360.1 (i.e., >= 15.0.2000.5 and < 15.0.2110.4, or >= 15.0.4003.23 and < 15.0.4360.2)
  3. Check SQL Server 2022 version
    Open SQL Server Configuration Manager or run 'SELECT @@VERSION' in SQL Server Management Studio, or check the SQL Server version via Registry under HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL16.InstanceName\CurrentVersion
    Affected if Version is 16.0.1000.6 through 16.0.1115.0, or 16.0.4003.1 through 16.0.4120.0 (i.e., >= 16.0.1000.6 and < 16.0.1115.1, or >= 16.0.4003.1 and < 16.0.4120.1)
  4. Verify OLE DB provider usage
    Review application connection strings for 'Provider=MSOLEDBSQL' or 'Provider=SQLOLEDB' (the latter is legacy). Check IIS or application host configurations for any OLE DB data source definitions, or inspect ODBC Data Source Administrator for OLE DB driver references
    Affected if Applications or services are actively using OLE DB connections to SQL Server using the vulnerable driver

You are affected if any SQL Server 2019/2022 or OLE DB Driver for SQL Server installation matches the vulnerable version ranges AND OLE DB connections are in use

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 as soon as they become available, or upgrade to patched versions. Prioritize affected SQL Server and dependent applications in the deployment environment.

Recommended fix High confidence

OLE DB Driver 18.7.0002.0/19.3.0003.0; SQL Server 2019 15.0.4360.2; SQL Server 2022 16.0.4120.1

  1. 1. Identify the specific SQL Server or OLE DB Driver version currently installed
  2. 2. For OLE DB Driver for SQL Server: Upgrade to version 18.7.0002.0 or 19.3.0003.0 (or later) from Microsoft's official download channels
  3. 3. For SQL Server 2019: Upgrade to version 15.0.2110.4 or 15.0.4360.2 (or later) via SQL Server servicing updates
  4. 4. For SQL Server 2022: Upgrade to version 16.0.1115.1 or 16.0.4120.1 (or later) via SQL Server servicing updates
  5. 5. Apply the update during a planned maintenance window following standard SQL Server patching procedures
  6. 6. Test application connectivity and functionality after the upgrade
Caveat Standard SQL Server upgrade risks apply - test in non-production environment first; ensure application compatibility with the new driver version

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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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