dbcve.org
Sql Server 2016Application · Microsoft

CVE-2024-49017

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-122

Data overflows a buffer allocated on the heap, corrupting neighbouring heap structures and allocator metadata that a patient attacker can groom into control of execution. It is subtler than a stack overflow but just as dangerous. The fix is validating lengths before every write and using safe allocators and bounded operations.

General guidance for the heap-based buffer overflow 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: Cumulative Update 19 (13.0.7050.2) or later; SQL Server 2017: Cumulative Update 32 (14.0.3485.1) or later; SQL Server 2019: Cumulative Update 25 (15.0.4410.1) or later

  1. 1. Identify the exact version of SQL Server 2016, 2017, or 2019 currently installed by running: SELECT @@VERSION
  2. 2. For SQL Server 2016 (13.0.6300.2 to 13.0.6455.1 or 13.0.7000.253 to 13.0.7049.2): Apply Cumulative Update 19 for SQL Server 2016 SP3 (version 13.0.7050.2) or later from https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2016/build-changes
  3. 3. For SQL Server 2017 (14.0.1000.169 to 14.0.2069.9 or 14.0.3006.16 to 14.0.3484.1): Apply Cumulative Update 32 for SQL Server 2017 (version 14.0.3485.1) or later from https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2017/build-changes
  4. 4. For SQL Server 2019 (15.0.2000.5 to 15.0.2130.2 or 15.0.4003.23 to 15.0.4409.1): Apply Cumulative Update 25 for SQL Server 2019 (version 15.0.4410.1) or later from https://learn.microsoft.com/en-us/troubleshoot/sql/releases/sqlserver-2019/build-changes
  5. 5. Download and install the appropriate cumulative update from the Microsoft Update Catalog or via Windows Update
  6. 6. After installation, restart the SQL Server service and verify the new version using: SELECT @@VERSION
  7. 7. Test critical database applications to ensure compatibility with the patched version
Caveat Review release notes for any known compatibility issues; test applications in a staging environment before deploying to production; note that cumulative updates include all previous hotfixes

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 $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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