dbcve.org
Sql Server 2016Application · Microsoft

CVE-2024-21333

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 exists in the SQL Server Native Client OLE DB Provider. The vulnerability has a CVSS score of 8.8 (HIGH), indicating it is network-exploitable and can lead to complete compromise of the affected system.

MitigationApply the appropriate Microsoft security update for SQL Server Native Client OLE DB Provider. Prioritize patching for any internet-facing SQL Server systems running the native client OLE DB interfaces.

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 installation and version
    Open SQL Server Configuration Manager or run 'SELECT @@VERSION' in SQLCMD to retrieve the installed SQL Server version and build number.
    Affected if The installed version 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 (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.11
  2. Confirm SQL Server Native Client OLE DB Provider is installed
    Check the Windows Registry under HKLM\SOFTWARE\Microsoft\Microsoft SQL Server\SQL_<InstanceName>\Providers or look for 'SQLOLEDB' in the list of OLE DB providers via SQL Server Management Studio under Server Objects > Linked Servers > Providers.
    Affected if The SQLOLEDB provider appears in the list of installed OLE DB providers for the SQL Server instance.
  3. Verify OLE DB Provider is actively in use
    Query sys.servers with provider='SQLOLEDB' or inspect application connection strings for 'Provider=SQLOLEDB' or 'Provider=SQLNCLI11' to determine if any applications or linked servers use the Native Client OLE DB interfaces.
    Affected if Any linked server, distributed query, or application connection string references the SQL Server Native Client OLE DB provider.

You are affected if your SQL Server version is within the affected ranges AND the SQL Server Native Client OLE DB Provider (SQLOLEDB) 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 the appropriate Microsoft security update for SQL Server Native Client OLE DB Provider. Prioritize patching for any internet-facing SQL Server systems running the native client OLE DB interfaces.

Recommended fix High confidence

SQL Server 2016: CU14 (13.0.6441.1) or CU22 (13.0.7037.1); SQL Server 2017: CU31 (14.0.2056.2) or CU26 (14.0.3471.2); SQL Server 2019: CU23 (15.0.2116.2) or CU30 (15.0.4382.1); SQL Server 2022: CU12 (16.0.1121.4) or CU6 (16.0.4131.2)

  1. 1. Identify the exact SQL Server version currently installed by running: SELECT @@VERSION
  2. 2. Based on your SQL Server version (2016, 2017, 2019, or 2022), apply the corresponding Cumulative Update (CU) that contains the fix:
  3. - SQL Server 2016: Apply CU14 (13.0.6441.1) or later for versions 13.0.6300.2-13.0.6441.0; Apply CU22 (13.0.7037.1) or later for versions 13.0.7000.253-13.0.7037.0
  4. - SQL Server 2017: Apply CU31 (14.0.2056.2) or later for versions 14.0.1000.169-14.0.2056.1; Apply CU26 (14.0.3471.2) or later for versions 14.0.3006.16-14.0.3471.1
  5. - SQL Server 2019: Apply CU23 (15.0.2116.2) or later for versions 15.0.2000.5-15.0.2116.1; Apply CU30 (15.0.4382.1) or later for versions 15.0.4003.23-15.0.4382.0
  6. - SQL Server 2022: Apply CU12 (16.0.1121.4) or later for versions 16.0.1000.6-16.0.1121.3; Apply CU6 (16.0.4131.2) or later for versions 16.0.4003.1-16.0.4131.1
  7. 3. Download and install the appropriate Cumulative Update from the Microsoft Update Catalog or through Windows Update
  8. 4. After installation, verify the version has been updated by running: SELECT @@VERSION
Caveat Standard Cumulative Update considerations apply - review release notes for any known issues; test in non-production environment before deploying to production

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-21333 — 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-21333 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