dbcve.org
Sql Server 2016Application · Microsoft

CVE-2024-43459

HIGH · 8.8 CVSS v3.1 Published 2024-11-12
Fix available
A fix is available. Upgrade to 13.0.6455.2 / 13.0.7050.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Patch available

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 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
How this class of weakness works · CWE-416

Memory is used after it has been freed, so its contents — now potentially attacker-controlled — drive the program's behaviour. With careful heap grooming this becomes code execution. The fix requires disciplined ownership of memory and often a targeted rework of the object lifecycle.

General guidance for the use after free class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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.6455.2>= 13.0.7000.253, < 13.0.7050.2
Sql Server 2017Application
Affected:>= 14.0.1000.169, < 14.0.2070.1>= 14.0.3006.16, < 14.0.3485.1
Sql Server 2019Application
Affected:>= 15.0.2000.5, < 15.0.2130.3>= 15.0.4003.23, < 15.0.4410.1

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

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.6455.2 / 13.0.7050.2 / 14.0.2070.1 or later
Fixed in 13.0.6455.213.0.7050.214.0.2070.1
Vendor patch msrc.microsoft.com →
Recommended fix High confidence

SQL Server 2016: upgrade to 13.0.6455.2 or 13.0.7050.2 | SQL Server 2017: upgrade to 14.0.2070.1 or 14.0.3485.1 | SQL Server 2019: upgrade to 15.0.2130.3 or 15.0.4410.1

  1. Identify the current SQL Server version by running: SELECT @@VERSION
  2. Determine the appropriate patch based on your current version and edition from the affected version ranges provided
  3. Apply the latest cumulative update (CU) that includes the fix for CVE-2024-43459. For SQL Server 2016: apply CU14 (13.0.7050.2) or CU21 (13.0.6455.2); for SQL Server 2017: apply CU31 (14.0.3485.1) or CU26 (14.0.2070.1); for SQL Server 2019: apply CU24 (15.0.4410.1) or CU18 (15.0.2130.3)
  4. Download the appropriate cumulative update from the Microsoft Catalog: https://www.catalog.update.microsoft.com/
  5. Back up all critical databases before applying any update
  6. Apply the cumulative update following Microsoft's installation guidelines
  7. Verify the update was successful by checking: SELECT @@VERSION
  8. Restart SQL Server services as required by the update
Caveat Standard cumulative update risks apply - test in non-production environment first; some updates may require downtime

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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