dbcve.org
Ole Db Driver For Sql ServerApplication · Microsoft

CVE-2024-28908

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 vulnerability that allows remote code execution. An attacker can exploit this by sending specially crafted requests to a system using the vulnerable OLE DB driver, potentially allowing execution of arbitrary code in the context of the application using the driver.

MitigationApply the relevant Microsoft security update for the OLE DB Driver for SQL Server. Identify all systems and applications using the vulnerable driver and ensure they are updated to a patched 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 Programs and Features (appwiz.cpl) and look for 'Microsoft OLE DB Driver for SQL Server' or run 'msiexec /x' to list installed MSI packages. Check the version in the program name or details.
    Affected if Version is 18.0.2 through 18.7.0002.0 (exclusive of 18.7.0002.0), or 19.0.0 through 19.3.0003.0 (exclusive of 19.3.0003.0)
  2. Check SQL Server 2019 instance version
    Open SQL Server Configuration Manager, go to SQL Server Services, or run 'SELECT @@VERSION' on each instance. Locate the build number (e.g., 15.0.2100.4).
    Affected if Build is 15.0.2000.5 through 15.0.2110.4 (exclusive of 15.0.2110.4), or 15.0.4003.23 through 15.0.4360.2 (exclusive of 15.0.4360.2)
  3. Check SQL Server 2022 instance version
    Open SQL Server Configuration Manager, go to SQL Server Services, or run 'SELECT @@VERSION' on each instance. Locate the build number (e.g., 16.0.1100.5).
    Affected if Build is 16.0.1000.6 through 16.0.1115.1 (exclusive of 16.0.1115.1), or 16.0.4003.1 through 16.0.4120.1 (exclusive of 16.0.4120.1)
  4. Identify applications using OLE DB connections
    Search application configuration files (.config, .xml, .json) for 'oledb' connection strings or 'SQLOLEDB' provider references. Review IIS application pools and .NET applications for OLE DB data source usage.
    Affected if Any application config references the OLE DB driver for SQL Server and connects to a vulnerable SQL Server instance or uses a vulnerable driver version

You are affected if Microsoft OLE DB Driver for SQL Server version 18.x before 18.7.0002.0 or 19.x before 19.3.0003.0 is installed, or if SQL Server 2019 or 2022 instances run vulnerable builds as specified in the version ranges.

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 relevant Microsoft security update for the OLE DB Driver for SQL Server. Identify all systems and applications using the vulnerable driver and ensure they are updated to a patched 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 or CU17 depending on branch; SQL Server 2022 to CU8 or CU3 depending on branch

  1. 1. Identify the exact version of Microsoft OLE DB Driver for SQL Server or SQL Server instance currently installed
  2. 2. For OLE DB Driver 18.x: Upgrade to version 18.7.0002.0 or later
  3. 3. For OLE DB Driver 19.x: Upgrade to version 19.3.0003.0 or later
  4. 4. For SQL Server 2019 (15.0.2000.5 branch): Apply Cumulative Update 24 (CU24) which includes version 15.0.2110.4 or later
  5. 5. For SQL Server 2019 (15.0.4003.23 branch): Apply Cumulative Update 17 (CU17) which includes version 15.0.4360.2 or later
  6. 6. For SQL Server 2022 (16.0.1000.6 branch): Apply Cumulative Update 8 (CU8) which includes version 16.0.1115.1 or later
  7. 7. For SQL Server 2022 (16.0.4003.1 branch): Apply Cumulative Update 3 (CU3) which includes version 16.0.4120.1 or later
  8. 8. Test the upgrade in a non-production environment before deploying to production
Caveat Standard SQL Server cumulative update considerations apply - test thoroughly in non-production; some updates may require service restart

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 / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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