dbcve.org
Sql Server 2016Application · Microsoft

CVE-2024-21335

HIGH · 8.8 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to 13.0.6441.1 / 13.0.7037.1 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
SQL Server Native Client OLE DB Provider 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 SQL Server Native Client OLE DB Provider. The vulnerability allows an authenticated attacker to execute arbitrary code on affected systems via specially crafted SQL queries or data payloads. The CVSS 8.8 score indicates significant exploitability with network-based attack vector.

MitigationApply Microsoft security updates for SQL Server Native Client OLE DB Provider when available, or upgrade to newer SQL Server versions that have discontinued the legacy OLE DB provider in favor of newer data access technologies.

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
Sql Server 2016Application
Affected:>= 13.0.6300.2, < 13.0.6441.1>= 13.0.7000.253, < 13.0.7037.1
Sql Server 2017Application
Affected:>= 14.0.1000.169, < 14.0.2056.2>= 14.0.3006.16, < 14.0.3471.2
Sql Server 2019Application
Affected:>= 15.0.2000.5, < 15.0.2116.2>= 15.0.4003.23, < 15.0.4382.1
Sql Server 2022Application
Affected:>= 16.0.1000.6, < 16.0.1121.4>= 16.0.4003.1, < 16.0.4131.2

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 installed SQL Server version
    Run the query 'SELECT @@VERSION' in SQL Server Management Studio or via sqlcmd command line. This displays the full version number including build number.
    Affected if The version number returned falls within any of the affected version ranges: 13.0.6300.2 to 13.0.6441.1, 13.0.7000.253 to 13.0.7037.1 for SQL Server 2016; 14.0.1000.169 to 14.0.2056.2, 14.0.3006.16 to 14.0.3471.2 for SQL Server 2017; 15.0.2000.5 to 15.0.2116.2, 15.0.4003.23 to 15.0.4382.1 for SQL Se
  2. Confirm SQL Server Native Client OLE DB Provider is installed
    Check the Windows registry under 'HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\SQLXXX\Providers' where XXX represents your SQL Server instance, or list providers via PowerShell command 'Get-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\*\Providers | Where-Object {$_.Name -like "*OLE DB*"}'.
    Affected if The SQL Server Native Client OLE DB Provider is listed among installed providers on the system.
  3. Identify OLE DB Provider version
    Query the version using PowerShell: '(Get-ItemProperty "C:\Windows\System32\msoledbsql.dll").VersionInfo.FileVersion' or check the provider DLL properties in Windows Explorer by right-clicking the DLL.
    Affected if The provider DLL version falls within the same affected version ranges as the SQL Server version above.
  4. Verify OLE DB Provider is in use
    Check application connection strings for 'Provider=MSOLEDBSQL' or review SQL Server logs for OLE DB provider connection activity using 'SELECT * FROM sys.dm_exec_sessions WHERE provider_desc = "OLE DB".'
    Affected if Applications are actively using the OLE DB provider via connection strings or the provider has recent connection activity in SQL Server.

You are affected if your SQL Server version is within the listed version ranges AND the SQL Server Native Client OLE DB Provider is installed and in use.

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 13.0.6441.1 / 13.0.7037.1 / 14.0.2056.2 or later
Fixed in 13.0.6441.113.0.7037.114.0.2056.2
Interim mitigation

Apply Microsoft security updates for SQL Server Native Client OLE DB Provider when available, or upgrade to newer SQL Server versions that have discontinued the legacy OLE DB provider in favor of newer data access technologies.

Recommended fix High confidence

SQL Server 2016 to CU30 (13.0.6441.1) or CU38 (13.0.7037.1); SQL Server 2017 to CU31 (14.0.2056.2) or CU42 (14.0.3471.2); SQL Server 2019 to CU22 (15.0.2116.2) or CU29 (15.0.4382.1); SQL Server 2022 to CU12 (16.0.1121.4) or CU21 (16.0.4131.2)

  1. 1. Identify current SQL Server version by running 'SELECT @@VERSION' in SQL Server Management Studio
  2. 2. Determine which version branch your current instance belongs to (2016, 2017, 2019, or 2022)
  3. 3. For SQL Server 2016: Upgrade to version 13.0.6441.1 (CU30) or version 13.0.7037.1 (CU38)
  4. 4. For SQL Server 2017: Upgrade to version 14.0.2056.2 (CU31) or version 14.0.3471.2 (CU42)
  5. 5. For SQL Server 2019: Upgrade to version 15.0.2116.2 (CU22) or version 15.0.4382.1 (CU29)
  6. 6. For SQL Server 2022: Upgrade to version 16.0.1121.4 (CU12) or version 16.0.4131.2 (CU21)
  7. 7. Download the appropriate Cumulative Update from microsoft.com/en-us/download or use Windows Update
  8. 8. Apply the update during a maintenance window, ensuring backups are current
Caveat Standard SQL Server cumulative update risks apply - test in non-production environment first; some updates may require restart

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

Fix this in Sql Server 2016 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-21335 — 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-21335 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