CVE-2024-49000: SQL Server Native Client Remote Code Execution Vulnerability
Published Nov 12, 2024
·Updated
SQL Server Native Client Remote Code Execution Vulnerability
Affected Software
14 affected componentsFixes available
Microsoft SQL Server 2017 (CU 31)
Microsoft SQL Server 2016 Azure Connect Feature Pack
Microsoft SQL Server 2019 (CU 29)
Microsoft SQL Server 2016
Microsoft SQL Server 2019
Microsoft SQL Server 2016>=13.0.6300.2<13.0.6455.2
Microsoft SQL Server 2016>=13.0.7000.253<13.0.7050.2
Microsoft SQL Server 2017>=14.0.1000.169<14.0.2070.1
Microsoft SQL Server 2017>=14.0.3006.16<14.0.3485.1
Microsoft SQL Server 2019>=15.0.2000.5<15.0.2130.3
Microsoft SQL Server 2019>=15.0.4003.23<15.0.4410.1
Microsoft SQL Server 2017
Microsoft SQL Server 2016
Microsoft SQL Server 2016 Azure Connect Feature Pack
Remediation
Event History
Nov 12, 2024
CVE Published
via Microsoft·08:00 AM
Data Sourced
via Microsoft·08:00 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:00 AM
Description
Updated
via Microsoft·08:00 AM
Affected Software
CVE Published
via MITRE·05:54 PM
Data Sourced
via MITRE·05:54 PM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2024-49000?
CVE-2024-49000 is classified as a remote code execution vulnerability affecting Microsoft SQL Server.
2
How do I fix CVE-2024-49000?
To fix CVE-2024-49000, you should apply the recommended patches for your affected version of SQL Server.
3
Which versions of SQL Server are affected by CVE-2024-49000?
CVE-2024-49000 affects Microsoft SQL Server 2016, 2017, and 2019, specifically certain builds within these versions.
4
What are the potential risks of CVE-2024-49000?
The potential risks of CVE-2024-49000 include unauthorized remote code execution, which can lead to data breaches or system compromises.
5
Is there a workaround for CVE-2024-49000 before applying the patch?
Currently, there is no specific workaround documented for CVE-2024-49000, so applying the patch is the recommended course of action.