dbcve.org
Sql Server 2016Application · Microsoft

CVE-2024-21332

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

A remote code execution vulnerability in SQL Server Native Client OLE DB Provider allows an authenticated attacker to execute arbitrary code on affected systems via specially crafted SQL queries or data packets.

MitigationApply Microsoft security updates for SQL Server and ensure all SQL Server Native Client installations are patched to current supported versions.

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 SQL Server version
    Run 'SELECT @@VERSION' in SQL Server query tool, or check the SQL Server error log, or view the version in SQL Server Configuration Manager under Server Name > Properties > General
    Affected if The version falls within any of these ranges: 13.0.6300.2 to 13.0.6441.1, 13.0.7000.253 to 13.0.7037.1 (SQL 2016); 14.0.1000.169 to 14.0.2056.2, 14.0.3006.16 to 14.0.3471.2 (SQL 2017); 15.0.2000.5 to 15.0.2116.2, 15.0.4003.23 to 15.0.4382.1 (SQL 2019); 16.0.1000.6 to 16.0.1121.4, 16.0.4003.1 to 16.0
  2. Confirm SQL Server Native Client OLE DB Provider is installed
    Search for sqlncli*.dll files on the system (typically in C:\Windows\System32 or C:\Program Files\Microsoft SQL Server\Client SDK), or check registry under HKLM\SOFTWARE\Microsoft\SQLServer for SQL Server Native Client entries
    Affected if SQL Server Native Client OLE DB Provider (sqlncli.dll) exists on the system and matches the vulnerable SQL Server version from step 1
  3. Check if OLE DB Provider is enabled for remote connections
    Review SQL Server surface area configuration or network protocol settings in SQL Server Configuration Manager. Look for 'Allow Inprocess' option for the Native Client OLE DB Provider in SQL Server Management Studio under Server Objects > Linked Servers > Providers
    Affected if The OLE DB Provider is enabled and accessible to authenticated users, which is the default configuration

Your SQL Server version falls within an affected range AND SQL Server Native Client OLE DB Provider is installed and accessible on your 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 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 and ensure all SQL Server Native Client installations are patched to current supported versions.

Recommended fix High confidence

Upgrade to the minimum fixed version for your version branch: SQL Server 2016 (13.0.6441.1 or 13.0.7037.1), SQL Server 2017 (14.0.2056.2 or 14.0.3471.2), SQL Server 2019 (15.0.2116.2 or 15.0.4382.1), SQL Server 2022 (16.0.1121.4 or 16.0.4131.2)

  1. 1. Identify the currently installed SQL Server version by running 'SELECT @@VERSION' or checking SQL Server Configuration Manager
  2. 2. Determine which version branch your current installation belongs to (2016, 2017, 2019, or 2022)
  3. 3. For SQL Server 2016: Upgrade to version 13.0.6441.1 (for builds >= 13.0.6300.2) or 13.0.7037.1 (for builds >= 13.0.7000.253)
  4. 4. For SQL Server 2017: Upgrade to version 14.0.2056.2 (for builds >= 14.0.1000.169) or 14.0.3471.2 (for builds >= 14.0.3006.16)
  5. 5. For SQL Server 2019: Upgrade to version 15.0.2116.2 (for builds >= 15.0.2000.5) or 15.0.4382.1 (for builds >= 15.0.4003.23)
  6. 6. For SQL Server 2022: Upgrade to version 16.0.1121.4 (for builds >= 16.0.1000.6) or 16.0.4131.2 (for builds >= 16.0.4003.1)
  7. 7. Download and apply the appropriate Cumulative Update (CU) or Service Stack Upgrade (SSU) from Microsoft Update Catalog or Microsoft Download Center
  8. 8. Test the upgrade in a non-production environment before applying to production
Caveat Standard SQL Server upgrade considerations apply; review release notes for behavior changes and ensure application compatibility testing is performed

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
  • 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-21332 — 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-21332 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