Microsoft SQL Server 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.
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.
5058721: 5058721, Security update for SQL Server 2022 CU19+GDR: Security update for SQL Server 2022 CU19+GDR, 16.0.4200.1: 16.0.4200.1, 16.0.4003.1 - 16.0.4195.2: 16.0.4003.1 - 16.0.4195.2, KB 5054531 - SQL2022 RTM CU19: KB 5054531 - SQL2022 RTM CU19, 5058712: 5058712, Security update for SQL Server 2022 RTM+GDR: Security update for SQL Server 2022 RTM+GDR, 16.0.1140.6: 16.0.1140.6, 16.0.1000.6 - 16.0.1135.2: 16.0.1000.6 - 16.0.1135.2, KB 5054833 - SQL2019 RTM CU32: KB 5054833 - SQL2019 RTM CU32, 5058722: 5058722, Security update for SQL Server 2019 CU32+GDR: Security update for SQL Server 2019 CU32+GDR, 15.0.4435.7: 15.0.4435.7, 15.0.4003.23 - 15.0.4430.1: 15.0.4003.23 - 15.0.4430.1, KB 5046365 - SQL2019 RTM CU29: KB 5046365 - SQL2019 RTM CU29, 5058713: 5058713, Security update for SQL Server 2019 RTM+GDR: Security update for SQL Server 2019 RTM+GDR, 15.0.2135.5: 15.0.2135.5, 15.0.2000.5 - 15.0.2130.3: 15.0.2000.5 - 15.0.2130.3, KB 5046859 - Previous SQL2019 RTM GDR: KB 5046859 - Previous SQL2019 RTM GDR, 5058714: 5058714, Security update for SQL Server 2017 CU31+GDR: Security update for SQL Server 2017 CU31+GDR, 14.0.3495.9: 14.0.3495.9, 14.0.3006.16 - 14.0.3490.10: 14.0.3006.16 - 14.0.3490.10, KB 5050533 - Previous SQL2017 RTM CU31 GDR: KB 5050533 - Previous SQL2017 RTM CU31 GDR, 5058716: 5058716, Security update for SQL Server 2017 RTM+GDR: Security update for SQL Server 2017 RTM+GDR, 14.0.2075.8: 14.0.2075.8, 14.0.1000.169 - 14.0.2070.1: 14.0.1000.169 - 14.0.2070.1, KB 5046857 - Previous SQL2017 RTM GDR: KB 5046857 - Previous SQL2017 RTM GDR, 5058717: 5058717, Security update for SQL 2016 Azure Connect Feature Pack: Security update for SQL 2016 Azure Connect Feature Pack, 13.0.7055.9: 13.0.7055.9, 13.0.7000.253 - 13.0.7050.2: 13.0.7000.253 - 13.0.7050.2, KB 5046856 - Previous SQL2016 Azure Connect Feature Pack GDR: KB 5046856 - Previous SQL2016 Azure Connect Feature Pack GDR, 5058718: 5058718, Security update for SQL Server 2016 SP3 RTM+GDR: Security update for SQL Server 2016 SP3 RTM+GDR, 13.0.6460.7: 13.0.6460.7, 13.0.6300.2 - 13.0.6455.2: 13.0.6300.2 - 13.0.6455.2, KB 5046855 - Previous SQL2016 RTM GDR: KB 5046855 - 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.

How could an attacker exploit this vulnerability?
An authenticated attacker would need to run a specially crafted query against a vulnerable SQL Server.

According to the CVSS metric, the attack complexity is high (AC:H). What does that mean for this vulnerability?
Successful exploitation of this vulnerability requires an attacker to take additional actions prior to exploitation to prepare the target environment.

According to the CVSS metric, a successful exploitation could lead to a scope change (S:C). What does this mean for this vulnerability?
Successful exploitation of this vulnerability could allow an attacker to escape the context of the SQL server and execute code on the host.

Security updates
15.0.2135.5 — https://support.microsoft.com/help/5058713
16.0.1140.6 — https://support.microsoft.com/help/5058712
15.0.4435.7 — https://support.microsoft.com/help/5058722
16.0.4200.1 — https://support.microsoft.com/help/5058721