dbcve.org
Ole Db Driver For Sql ServerApplication · Microsoft

CVE-2024-29048

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

This is a Remote Code Execution vulnerability in Microsoft OLE DB Driver for SQL Server. The vulnerability allows an attacker to execute arbitrary code on affected systems via the OLE DB driver, likely through specially crafted SQL Server connections or queries. The HIGH CVSS score (8.8) indicates significant potential impact if exploited.

MitigationApply Microsoft security updates for the OLE DB Driver for SQL Server once released; prior to patch availability, restrict network access to SQL Server instances and validate least-privilege database user accounts.

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\MSOLAP' -ErrorAction SilentlyContinue | Select-Object Version; also check for msoledbsql driver via: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\msoledbsql' -ErrorAction SilentlyContinue | Select-Object Version
    Affected if Installed version falls within >= 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 Management Studio or run: SELECT @@VERSION in a SQL query; alternatively check registry at HKLM:\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL15.INSTANCEID\Setup for the Version value
    Affected if Installed version falls within >= 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 Management Studio or run: SELECT @@VERSION in a SQL query; alternatively check registry at HKLM:\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL16.INSTANCEID\Setup for the Version value
    Affected if Installed version falls within >= 16.0.1000.6 and < 16.0.1115.1, OR >= 16.0.4003.1 and < 16.0.4120.1
  4. Confirm OLE DB Provider usage
    Check application configuration files (web.config, app.config) for connection strings containing 'Provider=MSOLEDBSQL' or 'Provider=msoledbsql' or review installed OLE DB providers via: Get-OleDbProvider in PowerShell
    Affected if Applications are using the OLE DB driver (MSOLEDBSQL) to connect to SQL Server on affected versions

Environment is affected if either the Microsoft OLE DB Driver for SQL Server is installed at a vulnerable version, OR SQL Server 2019/2022 is running at a vulnerable version and the system accepts OLE DB connections.

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 once released; prior to patch availability, restrict network access to SQL Server instances and validate least-privilege database user accounts.

Recommended fix High confidence

Microsoft OLE DB Driver 18.7.0002.0 / 19.3.0003.0; SQL Server 2019 CU23 or CU30; SQL Server 2022 CU12 or CU19

  1. For OLE DB Driver for SQL Server 18.x: Upgrade to version 18.7.0002.0 or later
  2. For OLE DB Driver for SQL Server 19.x: Upgrade to version 19.3.0003.0 or later
  3. For SQL Server 2019 (15.0.2xxx builds): Apply SQL Server 2019 CU23 (KB5036278) which contains build 15.0.2110.4 or later
  4. For SQL Server 2019 (15.0.4xxx builds): Apply SQL Server 2019 CU30 (KB5036982) which contains build 15.0.4360.2 or later
  5. For SQL Server 2022 (16.0.1xxx builds): Apply SQL Server 2022 CU12 (KB5035483) which contains build 16.0.1115.1 or later
  6. For SQL Server 2022 (16.0.4xxx builds): Apply SQL Server 2022 CU19 (KB5036980) which contains build 16.0.4120.1 or later
  7. After applying updates, verify the version using: SELECT @@VERSION
Caveat Standard SQL Server cumulative update considerations apply - test in non-production environment first; OLE DB Driver is a component-level update with minimal breaking change risk

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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