CVE-2024-49021: Microsoft SQL Server Remote Code Execution Vulnerability
Published Nov 12, 2024
·Updated
Microsoft SQL Server Remote Code Execution Vulnerability
Affected Software
16 affected componentsFixes available
Microsoft SQL Server 2017 (CU 31)
Microsoft SQL Server 2022 (CU 15)
Microsoft SQL Server 2016 Azure Connect Feature Pack
Microsoft SQL Server 2019 (CU 29)
Microsoft SQL Server 2022
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 2022>=16.0.1000.6<16.0.1135.2
Microsoft SQL Server 2022>=16.0.4003.1<16.0.4155.4
Microsoft SQL Server 2017
Remediation
Event History
Nov 12, 2024
CVE Published
via Microsoft·08:00 AM
Data Sourced
via Microsoft·08:00 AM
DescriptionSeverityWeakness
CVE Published
via MITRE·05:54 PM
Data Sourced
via MITRE·05:54 PM
DescriptionSeverity
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2024-49021?
CVE-2024-49021 is a remote code execution vulnerability with a critical severity rating.
2
How do I fix CVE-2024-49021?
To fix CVE-2024-49021, apply the relevant security patches and updates for your version of Microsoft SQL Server.
3
Which versions of Microsoft SQL Server are affected by CVE-2024-49021?
CVE-2024-49021 affects Microsoft SQL Server 2016, 2017, 2019, and 2022.
4
What are the potential impacts of CVE-2024-49021?
Exploitation of CVE-2024-49021 could allow an attacker to execute arbitrary code on the vulnerable SQL Server.
5
Is there a workaround for CVE-2024-49021?
As of now, the recommended action is to apply patches as there are no known workarounds for CVE-2024-49021.