CVE-2024-21373: SQL Server Native Client OLE DB Provider Remote Code Execution Vulnerability
Published Jul 9, 2024
·Updated
SQL Server Native Client OLE DB Provider Remote Code Execution Vulnerability
Affected Software
16 affected componentsFixes available
Microsoft SQL Server 2017 (CU 31)
Microsoft SQL Server 2019 (CU 27)
Microsoft SQL Server 2022 (CU 13)
Microsoft SQL Server 2016 Azure Connect Feature Pack
Microsoft SQL Server 2022
Microsoft SQL Server 2016
Microsoft SQL Server 2019
Microsoft SQL Server 2016>=13.0.6300.2<13.0.6441.1
Microsoft SQL Server 2016>=13.0.7000.253<13.0.7037.1
Microsoft SQL Server 2017>=14.0.1000.169<14.0.2056.2
Microsoft SQL Server 2017>=14.0.3006.16<14.0.3471.2
Microsoft SQL Server 2019>=15.0.2000.5<15.0.2116.2
Microsoft SQL Server 2019>=15.0.4003.23<15.0.4382.1
Microsoft SQL Server 2022>=16.0.1000.6<16.0.1121.4
Microsoft SQL Server 2022>=16.0.4003.1<16.0.4131.2
Microsoft SQL Server 2017
Event History
Jul 9, 2024
CVE Published
via Microsoft·07:00 AM
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
CVE Published
via MITRE·05:02 PM
Data Sourced
via MITRE·05:02 PM
DescriptionSeverity
Data Sourced
via NVD·05:15 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2024-21373?
CVE-2024-21373 is classified as a remote code execution vulnerability in SQL Server Native Client OLE DB Provider.
2
How does CVE-2024-21373 affect Microsoft SQL Server?
CVE-2024-21373 can allow an attacker to execute arbitrary code on the affected SQL Server installations.
3
How do I fix CVE-2024-21373?
To fix CVE-2024-21373, apply the appropriate patches released by Microsoft for the affected SQL Server versions.
4
Which versions of SQL Server are impacted by CVE-2024-21373?
CVE-2024-21373 affects Microsoft SQL Server 2016, 2017, 2019, and 2022.
5
What are the recommended actions for CVE-2024-21373?
It is recommended to update to the latest patched version of SQL Server to mitigate CVE-2024-21373.