SQL Server Native Client OLE DB Provider Remote Code Execution Vulnerability

How could an attacker exploit this vulnerability?
An attacker could exploit the vulnerability by tricking an authenticated user (UI:R) into attempting to connect to a malicious SQL server database via a connection driver (for example: OLE DB or OLEDB as applicable). This could result in the database returning malicious data that could cause arbitrary code execution on the client.

I am running SQL Server on my system. What action do I need to take?
Update your relevant version of SQL Server. Any applicable driver fixes are included in those updates.
Update your application to use Microsoft OLE DB Driver 18 or 19. Update the drivers to the versions listed on this page, which provide protection against this vulnerability.
Consult with your application vendor if it is compatible with Microsoft OLE DB Driver 18 or 19. Update the drivers to the versions listed in this page, which provide protection against this vulnerability
First, determine your SQL Server version number. For more information on determining your SQL Server version number, see Microsoft Knowledge Base Article 321185 - How to determine the version, edition, and update level of SQL Server and its components., Second, in the table below, locate your version number or the version range that your version number falls within. The corresponding update is the one you need to install.
5040939: 5040939, Security update for SQL Server 2022 CU13+GDR: Security update for SQL Server 2022 CU13+GDR, 16.0.4003.1 - 16.0.4125.3: 16.0.4003.1 - 16.0.4125.3, KB 5036432 - SQL2022 RTM CU13: KB 5036432 - SQL2022 RTM CU13, 5040936: 5040936, Security update for SQL Server 2022 RTM+GDR: Security update for SQL Server 2022 RTM+GDR, 16.0.1000.6 - 16.0.1115.1: 16.0.1000.6 - 16.0.1115.1, KB 5035432 - Previous SQL2022 RTM GDR: KB 5035432 - Previous SQL2022 RTM GDR, 5040948: 5040948, Security update for SQL Server 2019 CU27+GDR: Security update for SQL Server 2019 CU27+GDR, 15.0.4003.23 - 15.0.4375.4: 15.0.4003.23 - 15.0.4375.4, KB 5037331 - SQL2019 RTM CU27: KB 5037331 - SQL2019 RTM CU27, 5040986: 5040986, Security update for SQL Server 2019 RTM+GDR: Security update for SQL Server 2019 RTM+GDR, 15.0.2000.5 - 15.0.2110.4: 15.0.2000.5 - 15.0.2110.4, KB 5035434 - Previous SQL2019 RTM GDR: KB 5035434 - Previous SQL2019 RTM GDR, 5040940: 5040940, Security update for SQL Server 2017 CU31+GDR: Security update for SQL Server 2017 CU31+GDR, 14.0.3006.16 - 14.0.3465.1: 14.0.3006.16 - 14.0.3465.1, KB 5029376 - SQL2017 RTM CU31: KB 5029376 - SQL2017 RTM CU31, 5040942: 5040942, Security update for SQL Server 2017 RTM+GDR: Security update for SQL Server 2017 RTM+GDR, 14.0.1000.169 - 14.0.2052.1: 14.0.1000.169 - 14.0.2052.1, KB 5029375 - Previous SQL2017 RTM GDR: KB 5029375 - Previous SQL2017 RTM GDR, 5040944: 5040944, Security update for SQL 2016 Azure Connect Feature Pack: Security update for SQL 2016 Azure Connect Feature Pack, 13.0.7000.253 - 13.0.7029.3: 13.0.7000.253 - 13.0.7029.3, KB 5029187 - SQL2016 Azure Connect Feature Pack: KB 5029187 - SQL2016 Azure Connect Feature Pack, 5040946: 5040946, Security update for SQL Server 2016RTM+GDR: Security update for SQL Server 2016RTM+GDR, 13.0.6300.2 - 13.0.6435.1: 13.0.6300.2 - 13.0.6435.1, KB 5029186 - Previous SQL2016 RTM GDR: KB 5029186 - Previous SQL2016 RTM GDR
The General Distribution Release (GDR) and Cumulative Update (CU) designations correspond to the two different servicing options in place for SQL Server baseline releases. A baseline can be either an RTM release or a Service Pack release.
GDR updates – cumulatively only contain security updates for the given baseline., CU updates – cumulatively contain all functional fixes and security updates for the given baseline.
For any given baseline, either the GDR or CU updates could be options (see below).
If SQL Server installation is at a baseline version, you can choose either the GDR or CU update., If SQL Server installation has intentionally only installed past GDR updates, then choose to install the GDR update package., If SQL Server installation has intentionally installed previous CU updates, then chose to install the CU security update package.
Yes. SQL Server instances on Windows Azure (IaaS) can be offered the security updates through Microsoft Update, or customers can download the security updates from Microsoft Download Center and apply them manually.

Security updates
14.0.2056.2 — https://support.microsoft.com/help/5040942
15.0.2116.2 — https://support.microsoft.com/help/5040986
13.0.6441.1 — https://support.microsoft.com/help/5040946
13.0.7037.1 — https://support.microsoft.com/help/5040944
14.0.3471.2 — https://support.microsoft.com/help/5040940
16.0.1121.4 — https://support.microsoft.com/help/5040936
16.0.4131.2 — https://support.microsoft.com/help/5040939
15.0.4382.1 — https://support.microsoft.com/help/5040948