Ole Db Driver For Sql ServerApplication · Microsoft

CVE-2024-29044

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 OLE DB Driver for SQL Server Remote Code Execution Vulnerability

Technical summary

dbcve analysis · moderate confidence

This is a Remote Code Execution vulnerability in the Microsoft OLE DB Driver for SQL Server. Given the CVSS score of 8.8 (HIGH), it is exploitable over the network and could allow an attacker to execute arbitrary code on affected systems without authentication, likely through specially crafted SQL Server connections or queries.

MitigationApply the Microsoft security update for the OLE DB Driver for SQL Server. If an immediate patch is not available, restrict network exposure of SQL Server systems and enforce authentication for database connections.

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

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

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.

Check if OLE DB Driver for SQL Server is installed

Open Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell and look for 'Microsoft OLE DB Driver for SQL Server' in the list of installed software

Affected if The driver is listed with a version that falls within 18.0.2 to 18.7.0002.0 (exclusive) or 19.0.0 to 19.3.0003.0 (exclusive)
Determine OLE DB Driver version

If installed, note the exact version number from the Programs and Features list or query the driver file version at the installation path (typically C:\Program Files\Microsoft OLE DB Driver for SQL Server\oledb.dll) using 'Get-ItemProperty' or right-clicking the file > Properties > Details

Affected if The 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
Check SQL Server 2019 installation and version

Open SQL Server Configuration Manager, or run 'SELECT @@VERSION' in SQL Server Management Studio (SSMS), or check the registry key HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL15.INSTANCEID\Setup

Affected if SQL Server 2019 is installed with a version between 15.0.2000.5 and 15.0.2110.4 (exclusive) or between 15.0.4003.23 and 15.0.4360.2 (exclusive)
Check SQL Server 2022 installation and version

Open SQL Server Configuration Manager, or run 'SELECT @@VERSION' in SQL Server Management Studio (SSMS), or check the registry key HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL16.INSTANCEID\Setup

Affected if SQL Server 2022 is installed with a version between 16.0.1000.6 and 16.0.1115.1 (exclusive) or between 16.0.4003.1 and 16.0.4120.1 (exclusive)

You are affected if OLE DB Driver for SQL Server versions 18.0.2-18.7.0002.0 or 19.0.0-19.3.0003.0 are installed, or if SQL Server 2019 versions 15.0.2000.5-15.0.2110.4 or 15.0.4003.23-15.0.4360.2 are running, or if SQL Server 2022 versions 16.0.1000.6-16.0.1115.1 or 16.0.4003.1-16.0.4120.1 are running.

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 the Microsoft security update for the OLE DB Driver for SQL Server. If an immediate patch is not available, restrict network exposure of SQL Server systems and enforce authentication for database connections.

Recommended fix High confidence

OLE DB Driver 18.7.0002.0+ / OLE DB Driver 19.3.0003.0+ / SQL Server 2019 15.0.2110.4+ or 15.0.4360.2+ / SQL Server 2022 16.0.1115.1+ or 16.0.4120.1+

Identify the exact version of Microsoft OLE DB Driver for SQL Server or SQL Server currently installed
For OLE DB Driver 18.x users: Upgrade to version 18.7.0002.0 or later
For OLE DB Driver 19.x users: Upgrade to version 19.3.0003.0 or later
For SQL Server 2019 users: Upgrade to version 15.0.2110.4 or later (for builds 15.0.2000.5 through 15.0.2099.x), or to version 15.0.4360.2 or later (for builds 15.0.4003.23 through 15.0.4099.x)
For SQL Server 2022 users: Upgrade to version 16.0.1115.1 or later (for builds 16.0.1000.6 through 16.0.1099.x), or to version 16.0.4120.1 or later (for builds 16.0.4003.1 through 16.0.4099.x)
Download the appropriate update from the Microsoft Security Response Center (msrc.microsoft.com) or Microsoft Update Catalog
Test the upgrade in a non-production environment before deploying to production

Caveat Upgrading SQL Server may require downtime and compatibility testing with existing applications; review release notes for any behavioral changes

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-29044 — 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-29044 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-29044?

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: Ole Db Driver For Sql Server

Remediation

A high-priority fix

Fix this in Ole Db Driver For Sql Server 28 hrs · Moderate

Typical engagement from $4,760

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2024-29044 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