dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-21441

HIGH · 8.8 CVSS v3.1 Published 2024-03-12
Fix available
A fix is available. Upgrade to 10.0.10240.20596 / 10.0.14393.6897 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 WDAC OLE DB provider 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 WDAC OLE DB provider for SQL Server contains a remote code execution vulnerability, allowing an attacker to execute arbitrary code on affected systems via the database provider interface. The CVSS 8.8 score indicates network-exploitable RCE with moderate attack complexity.

MitigationApply Microsoft security updates for SQL Server when released; until then, restrict network access to SQL Server ports and follow least-privilege database access principles.

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
Windows 10 1507Operating system
Affected:< 10.0.10240.20596
Windows 10 1607Operating system
Affected:< 10.0.14393.6897
Windows 10 1809Operating system
Affected:< 10.0.17763.5696
Windows 10 21h2Operating system
Affected:< 10.0.19044.4291
Windows 10 22h2Operating system
Affected:< 10.0.19045.4291
Windows 11 21h2Operating system
Affected:< 10.0.22000.2899
Windows 11 22h2Operating system
Affected:< 10.0.22621.3447
Windows 11 23h2Operating system
Affected:< 10.0.22631.3447

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. Identify Windows version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact Windows build
    Affected if The build number falls below any of these thresholds: 10240.20596 (1507), 14393.6897 (1607), 17763.5696 (1809), 19044.4291 (21h2/22h2), 22000.2899 (Win11 21h2), 22621.3447 (Win11 22h2), 22631.3447 (Win11 23h2)
  2. Verify SQL Server OLE DB provider installation
    Check for presence of the OLE DB provider files in the SQL Server installation directory (typically under Program Files\Microsoft SQL Server or Program Files (x86)\Microsoft SQL Server) and look for sqloledb.dll or related provider DLLs
    Affected if The OLE DB provider for SQL Server is installed and the Windows version is below the fixed builds
  3. Confirm provider is loaded or accessible
    Review installed OLE DB providers by checking registry key HKLM\SOFTWARE\Classes\OLEDB\Provider or use oledb32.dll enumeration tools if available
    Affected if The vulnerable WDAC OLE DB provider is registered and accessible on the system
  4. Check for active SQL Server connections using OLE DB
    Review SQL Server error logs and running processes for applications using OLE DB data source connections, particularly those connecting via 'SQLOLEDB' provider string
    Affected if Applications are actively using the OLE DB provider for SQL Server connections on an affected Windows version

A system is affected if it runs any Windows 10 or 11 version with a build number lower than the thresholds listed and has the SQL Server OLE DB provider installed and accessible.

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 10.0.10240.20596 / 10.0.14393.6897 / 10.0.17763.5696 or later
Fixed in 10.0.10240.2059610.0.14393.689710.0.17763.5696
Interim mitigation

Apply Microsoft security updates for SQL Server when released; until then, restrict network access to SQL Server ports and follow least-privilege database access principles.

Recommended fix High confidence

Windows 10 1507: Build 10.0.10240.20596 or later | Windows 10 1607: Build 10.0.14393.6897 or later | Windows 10 1809: Build 10.0.17763.5696 or later | Windows 10 21h2: Build 10.0.19044.4291 or later | Windows 10 22h2: Build 10.0.19045.4291 or later | Windows 11 21h2: Build 10.0.22000.2899 or later |

  1. Identify the current Windows version by running 'winver' or checking System Information
  2. Determine which Windows 10 or 11 version is installed and note the build number
  3. Apply the appropriate Windows Security Update for February 2024 (KB5002537 or subsequent updates) that addresses CVE-2024-21441
  4. Restart the system after applying the update to ensure the patch takes effect
  5. Verify the update was successfully installed by checking Windows Update history or running 'winver' to confirm the build number matches or exceeds the fixed version for your Windows edition
Caveat Standard Windows update risks apply - ensure backups and test in non-production environments before broad deployment in enterprise environments

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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