CVE-2024-43462: SQL Server Native Client Remote Code Execution Vulnerability
Published Nov 12, 2024
·Updated
SQL Server Native Client Remote Code Execution Vulnerability
Affected Software
12 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
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:53 PM
Data Sourced
via MITRE·05:53 PM
DescriptionSeverity
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2024-43462?
CVE-2024-43462 has been assessed with a critical severity rating due to its potential for remote code execution.
2
How do I fix CVE-2024-43462?
To fix CVE-2024-43462, apply the latest security patches provided by Microsoft for affected SQL Server versions.
3
Which SQL Server versions are affected by CVE-2024-43462?
CVE-2024-43462 affects SQL Server 2016, 2017, and 2019 across various cumulative updates.
4
What types of attacks can exploit CVE-2024-43462?
CVE-2024-43462 can be exploited by attackers to execute arbitrary code remotely on vulnerable SQL Server installations.
5
Is there a workaround for CVE-2024-43462?
Currently, the recommended mitigation for CVE-2024-43462 is to apply the security updates released by Microsoft.