dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-30006

HIGH · 8.8 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 10.0.10240.20651 / 10.0.14393.6981 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

This is a Remote Code Execution vulnerability in the Windows Data Access Components (WDAC) OLE DB provider for Microsoft SQL Server. The vulnerability allows an attacker to execute arbitrary code on affected systems, likely through malicious SQL queries or specially crafted database connections.

MitigationApply Microsoft security updates for this vulnerability when released. In the interim, restrict network access to SQL Server instances, enforce least-privilege database accounts, and disable the OLE DB provider if not required.

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.20651
Windows 10 1607Operating system
Affected:< 10.0.14393.6981
Windows 10 1809Operating system
Affected:< 10.0.17763.5820
Windows 10 21h2Operating system
Affected:< 10.0.19044.4412
Windows 10 22h2Operating system
Affected:< 10.0.19045.4412
Windows 11 21h2Operating system
Affected:< 10.0.22000.2960
Windows 11 22h2Operating system
Affected:< 10.0.22621.3593
Windows 11 23h2Operating system
Affected:< 10.0.22631.3593

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 Windows version against affected ranges
    Run 'winver' or 'systeminfo' to obtain the installed Windows build number. For Windows 10, look for builds below 10240.20651 (1507), 14393.6981 (1607), 17763.5820 (1809), 19044.4412 (21h2), or 19045.4412 (22h2). For Windows 11, look for builds below 22000.2960 (21h2), 22621.3593 (22h2), or 22631.3593 (23h2).
    Affected if The installed Windows build number falls below any of the listed threshold versions for the corresponding Windows release.
  2. Verify OLE DB provider presence
    Check for the presence of sqloledb.dll or the WDAC OLE DB provider files in the system. Common paths include C:\Windows\System32\ and C:\Windows\SysWOW64\. Use 'Get-ItemProperty' or 'dir' to enumerate these locations.
    Affected if The OLE DB provider DLL files exist on the system and the vulnerable code path is present.
  3. Confirm SQL Server OLE DB connections are in use
    Review SQL Server configuration and application connection strings for the use of 'Provider=SQLOLEDB' or OLE DB connectivity. Check SQL Server error logs and active connections for OLE DB provider usage.
    Affected if SQL Server instances accept OLE DB connections or applications connect using the OLE DB provider.

The system is affected if it runs a Windows version with a build number below the thresholds listed and has the WDAC OLE DB provider enabled or present on the system.

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.20651 / 10.0.14393.6981 / 10.0.17763.5820 or later
Fixed in 10.0.10240.2065110.0.14393.698110.0.17763.5820
Interim mitigation

Apply Microsoft security updates for this vulnerability when released. In the interim, restrict network access to SQL Server instances, enforce least-privilege database accounts, and disable the OLE DB provider if not required.

Recommended fix High confidence

Install KB5043735 or later cumulative update; fixed builds: Windows 10 1507 (10.0.10240.20651), Windows 10 1607 (10.0.14393.6981), Windows 10 1809 (10.0.17763.5820), Windows 10 21h2 (10.0.19044.4412), Windows 10 22h2 (10.0.19045.4412), Windows 11 21h2 (10.0.22000.2960), Windows 11 22h2 (10.0.22621.3

  1. Open Windows Settings by pressing Win+I
  2. Navigate to Windows Update in the left panel
  3. Click 'Check for updates' to download and install the latest security updates
  4. Alternatively, manually install the specificKB5043735or later cumulative update for your Windows version from the Microsoft Update Catalog
  5. Restart the system when prompted to complete the installation
  6. Verify the installed build number matches or exceeds the fixed version for your Windows release (e.g., Windows 10 22h2 should be 10.0.19045.4412 or higher)
Caveat Standard Windows update risks apply - ensure backups before updating in production environments

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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