CVE-2024-21415: 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-21415?
CVE-2024-21415 is classified as a critical vulnerability due to its potential to enable remote code execution.
2
How do I fix CVE-2024-21415?
To remediate CVE-2024-21415, apply the relevant security patch provided by Microsoft for your SQL Server version.
3
What products are affected by CVE-2024-21415?
CVE-2024-21415 affects multiple versions of Microsoft SQL Server, including SQL Server 2016, 2017, 2019, and 2022.
4
Can CVE-2024-21415 be exploited remotely?
Yes, CVE-2024-21415 can be exploited remotely, allowing an attacker to execute arbitrary code on the affected server.
5
What versions of SQL Server have CVE-2024-21415 vulnerabilities?
CVE-2024-21415 affects SQL Server 2016 (sp3), 2017 (GDR), 2019 (CU 27), and 2022 (CU 13) among others.