CVE-2024-37333: 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-37333?
CVE-2024-37333 has been rated with high severity due to its potential for remote code execution.
2
How do I fix CVE-2024-37333?
To fix CVE-2024-37333, apply the latest patches provided by Microsoft for the affected SQL Server versions.
3
Which versions of SQL Server are affected by CVE-2024-37333?
CVE-2024-37333 affects SQL Server 2016, 2017, 2019, and 2022 up to certain versions.
4
What are the potential impacts of CVE-2024-37333 exploitation?
If exploited, CVE-2024-37333 could allow an attacker to execute arbitrary code on the affected SQL Server.
5
Is there a known workaround for CVE-2024-37333?
Currently, the only recommended solution for CVE-2024-37333 is to install the available security updates directly from Microsoft.