CVE-2024-37336: SQL Server Native Client OLE DB Provider Remote Code Execution Vulnerability
First published: Tue Jul 09 2024(Updated: )
SQL Server Native Client OLE DB Provider Remote Code Execution Vulnerability
Credit: secure@microsoft.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Microsoft SQL Server 2019 for Linux Containers | ||
| Microsoft SQL Server 2017 | ||
| Microsoft SQL Server 2022 | ||
| Microsoft SQL Server 2016 Azure Connect Feature Pack | ||
| Microsoft SQL Server | ||
| Microsoft SQL Server | ||
| Microsoft SQL Server 2016 (CU 17) | ||
| Microsoft SQL Server 2016 (CU 17) | <13.0.6441.1 | |
| Microsoft SQL Server 2016 (CU 17) | >=13.0.7000.253<13.0.7037.1 | |
| Microsoft SQL Server | <14.0.2056.2 | |
| Microsoft SQL Server | >=14.0.3456.2<14.0.3471.2 | |
| Microsoft SQL Server | <15.0.2116.2 | |
| Microsoft SQL Server | >=15.0.4375.4<15.0.4382.1 | |
| Microsoft SQL Server | <16.0.1121.4 | |
| Microsoft SQL Server | >=16.0.4125.3<16.0.4131.2 | |
| Microsoft SQL Server |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
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.
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.
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.
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.
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.
- collector/msrc
- source/Microsoft
- agent/references
- agent/type
- agent/description
- agent/first-publish-date
- collector/msrc-cve
- agent/title
- agent/severity
- agent/weakness
- agent/author
- agent/event
- agent/remedy
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- agent/tags
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-api
- source/NVD
- vendor/microsoft
- canonical/microsoft sql server 2019 for linux containers
- canonical/microsoft sql server 2017
- canonical/microsoft sql server 2022
- canonical/microsoft sql server 2016 azure connect feature pack
- canonical/microsoft sql server
- canonical/microsoft sql server 2016 (cu 17)
- version/microsoft sql server 2016 (cu 17)/13.0.7000.253
- version/microsoft sql server/14.0.3456.2
- version/microsoft sql server/15.0.4375.4
- version/microsoft sql server/16.0.4125.3