CVE-2024-37336: 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 2019 (CU 27)
Microsoft SQL Server 2017 (CU 31)
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.6441.1
Microsoft SQL Server 2016>=13.0.7000.253<13.0.7037.1
Microsoft SQL Server 2017<14.0.2056.2
Microsoft SQL Server 2017>=14.0.3456.2<14.0.3471.2
Microsoft SQL Server 2019<15.0.2116.2
Microsoft SQL Server 2019>=15.0.4375.4<15.0.4382.1
Microsoft SQL Server 2022<16.0.1121.4
Microsoft SQL Server 2022>=16.0.4125.3<16.0.4131.2
Microsoft SQL Server 2017
Remediation
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-37336?
CVE-2024-37336 is classified as a remote code execution vulnerability, which can potentially allow attackers to execute arbitrary code on affected systems.
2
How do I fix CVE-2024-37336?
To mitigate CVE-2024-37336, it is recommended to apply the latest security patches provided by Microsoft for the affected SQL Server versions.
3
Which versions of SQL Server are affected by CVE-2024-37336?
CVE-2024-37336 affects Microsoft SQL Server 2016, 2017, 2019, and 2022 up to specified versions.
4
What types of attacks can CVE-2024-37336 facilitate?
CVE-2024-37336 can facilitate remote code execution attacks, allowing unauthorized execution of commands on the affected SQL Server.
5
Is there a workaround for CVE-2024-37336 if I cannot apply the patch immediately?
Currently, there is no documented workaround for CVE-2024-37336, so applying the patch is the recommended course of action.