dbcve.org
Sql Server 2016Application · Microsoft

CVE-2024-21308

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 allows an attacker to execute arbitrary code on affected systems via specially crafted network packets, potentially achieving SYSTEM-level privileges.

MitigationApply the relevant security update for SQL Server or disable the OLE DB Provider if unused, and restrict network access to SQL Server ports.

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 Management Studio or execute `sqlcmd -S localhost -Q "SELECT @@VERSION"` to retrieve the installed SQL Server version number.
    Affected if The version falls within any of the following ranges: 13.0.6300.2 to 13.0.6441.1, 13.0.7000.253 to 13.0.7037.1 (SQL Server 2016); 14.0.1000.169 to 14.0.2056.2, 14.0.3006.16 to 14.0.3471.2 (SQL Server 2017); 15.0.2000.5 to 15.0.2116.2, 15.0.4003.23 to 15.0.4382.1 (SQL Server 2019); 16.0.1000.6 to 16.
  2. Confirm OLE DB Provider is present
    Check the Windows Registry under `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SQLServer_CurrentVersion\Setup` for OLE DB components, or verify the presence of `sqloledb.dll` in the SQL Server installation directory (typically found in the `C:\Program Files\Microsoft SQL Server\<version>\Shared` folder).
    Affected if The OLE DB Provider (sqloledb.dll) is installed on the system.
  3. Check if OLE DB is enabled for network connections
    Review SQL Server configuration using `SELECT * FROM sys.dm_server_registry` or check Surface Area Configuration settings to determine if OLE DB provider is exposed to network connections.
    Affected if OLE DB Provider is enabled and accessible over the network, or the SQL Server instance is listening on TCP port 1433 (the default SQL Server port) with OLE DB provider active.

Your environment is affected if you are running any of the listed SQL Server versions AND the SQL Server Native Client OLE DB Provider is installed and enabled 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 the relevant security update for SQL Server or disable the OLE DB Provider if unused, and restrict network access to SQL Server ports.

Recommended fix High confidence

SQL Server 2016: Upgrade to 13.0.6441.1 (CU14) or 13.0.7037.1 (CU23); SQL Server 2017: Upgrade to 14.0.2056.2 (CU28) or 14.0.3471.2 (CU37); SQL Server 2019: Upgrade to 15.0.2116.2 (CU21) or 15.0.4382.1 (CU32); SQL Server 2022: Upgrade to 16.0.1121.4 (CU11) or 16.0.4131.2 (CU21)

  1. Identify the current SQL Server version by running 'SELECT @@VERSION' in SQL Server Management Studio
  2. Determine the appropriate CU version to install based on your current version (see upgrade_path)
  3. Download the corresponding Cumulative Update (CU) from Microsoft Update Catalog or Microsoft's SQL Server release notes
  4. Test the update in a non-production environment before applying to production
  5. Create a full backup of all databases, including system databases
  6. Schedule a maintenance window during low-usage period
  7. Stop SQL Server services if required by the CU installer
  8. Run the CU installer with administrator privileges
Caveat Standard SQL Server CU update with minimal risk; review release notes for any known issues 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
  • 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-21308 — 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-21308 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