SQL Server Native Client Remote Code Execution Vulnerability

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.
5046862: 5046862, Security update for SQL Server 2022 CU15+GDR: Security update for SQL Server 2022 CU15+GDR, 16.0.4003.1 - 16.0.4150.1: 16.0.4003.1 - 16.0.4150.1, KB 5046059 - SQL2022 RTM CU15 GDR: KB 5046059 - SQL2022 RTM CU15 GDR, 5046861: 5046861, Security update for SQL Server 2022 RTM+GDR: Security update for SQL Server 2022 RTM+GDR, 16.0.1000.6 - 16.0.1130.5: 16.0.1000.6 - 16.0.1130.5, KB 5046057 - SQL2022 RTM GDR: KB 5046057 - SQL2022 RTM GDR, 5046860: 5046860, Security update for SQL Server 2019 CU29+GDR: Security update for SQL Server 2019 CU29+GDR, 15.0.4003.23 - 15.0.4405.4: 15.0.4003.23 - 15.0.4405.4, KB 5046365 - SQL2019 RTM CU29: KB 5046365 - SQL2019 RTM CU29, 5046859: 5046859, Security update for SQL Server 2019 RTM+GDR: Security update for SQL Server 2019 RTM+GDR, 15.0.2000.5 - 15.0.2125.1: 15.0.2000.5 - 15.0.2125.1, KB 5046056 - SQL2019 RTM GDR: KB 5046056 - SQL2019 RTM GDR, 5046858: 5046858, Security update for SQL Server 2017 CU31+GDR: Security update for SQL Server 2017 CU31+GDR, 14.0.3006.16 - 14.0.3480.1: 14.0.3006.16 - 14.0.3480.1, KB 5046061 - SQL2017 RTM CU31 GDR: KB 5046061 - SQL2017 RTM CU31 GDR, 5046857: 5046857, Security update for SQL Server 2017 RTM+GDR: Security update for SQL Server 2017 RTM+GDR, 14.0.1000.169 - 14.0.2065.1: 14.0.1000.169 - 14.0.2065.1, KB 5046058 - SQL2017 RTM GDR: KB 5046058 - SQL2017 RTM GDR, 5046856: 5046856, Security update for SQL 2016 Azure Connect Feature Pack: Security update for SQL 2016 Azure Connect Feature Pack, 13.0.7000.253 - 13.0.7045.2: 13.0.7000.253 - 13.0.7045.2, KB 5046062 - SQL2016 Azure Connect Feature Pack GDR: KB 5046062 - SQL2016 Azure Connect Feature Pack GDR, 5046855: 5046855, Security update for SQL Server 2016 SP3 RTM+GDR: Security update for SQL Server 2016 SP3 RTM+GDR, 13.0.6300.2 - 13.0.6450.1: 13.0.6300.2 - 13.0.6450.1, KB 5046063 - SQL2016 RTM GDR: KB 5046063 - 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.

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.

Security updates
14.0.2070.1 — https://support.microsoft.com/help/5046857
15.0.2130.3 — https://support.microsoft.com/help/5046859
13.0.6455.2 — https://support.microsoft.com/help/5046855
13.0.7050.2 — https://support.microsoft.com/help/5046856
14.0.3485.1 — https://support.microsoft.com/help/5046858
15.0.4410.1 — https://support.microsoft.com/help/5046860