Microsoft SQL Server Elevation of Privilege Vulnerability

How could an attacker exploit this vulnerability?
An authenticated attacker with explicit permissions could exploit the vulnerability by logging in to the SQL server and could then elevate their privileges to sysadmin.

What privileges could be gained by an attacker who successfully exploited the vulnerability?
An attacker who successfully exploited this vulnerability could gain administrator privileges.

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 following table, locate your version number or the version range that your version number falls within. The corresponding update is the one you need to install.
5063814: 5063814, Security update for SQL Server 2022 CU20+GDR: Security update for SQL Server 2022 CU20+GDR, 16.0.4210.1: 16.0.4210.1, 16.0.4003.1 - 16.0.4205.1: 16.0.4003.1 - 16.0.4205.1, KB 5059390 - SQL2022 RTM CU20: KB 5059390 - SQL2022 RTM CU20, 5063756: 5063756, Security update for SQL Server 2022 RTM+GDR: Security update for SQL Server 2022 RTM+GDR, 16.0.1145.1: 16.0.1145.1, 16.0.1000.6 - 16.0.1140.6: 16.0.1000.6 - 16.0.1140.6, KB 5058712 - Previous SQL2022 RTM GDR: KB 5058712 - Previous SQL2022 RTM GDR, 5063757: 5063757, Security update for SQL Server 2019 CU32+GDR: Security update for SQL Server 2019 CU32+GDR, 15.0.4440.1: 15.0.4440.1, 15.0.4003.23 - 15.0.4435.7: 15.0.4003.23 - 15.0.4435.7, KB 5058722 - Previous SQL2019 RTM CU32 GDR: KB 5058722 - Previous SQL2019 RTM CU32 GDR, 5063758: 5063758, Security update for SQL Server 2019 RTM+GDR: Security update for SQL Server 2019 RTM+GDR, 15.0.2140.1: 15.0.2140.1, 15.0.2000.5 - 15.0.2135.5: 15.0.2000.5 - 15.0.2135.5, KB 5058713 - Previous SQL2019 RTM GDR: KB 5058713 - Previous SQL2019 RTM GDR, 5063759: 5063759, Security update for SQL Server 2017 CU31+GDR: Security update for SQL Server 2017 CU31+GDR, 14.0.3500.1: 14.0.3500.1, 14.0.3006.16 - 14.0.3495.9: 14.0.3006.16 - 14.0.3495.9, KB 5058714 - Previous SQL2017 RTM CU31 GDR: KB 5058714 - Previous SQL2017 RTM CU31 GDR, 5063760: 5063760, Security update for SQL Server 2017 RTM+GDR: Security update for SQL Server 2017 RTM+GDR, 14.0.2080.1: 14.0.2080.1, 14.0.1000.169 - 14.0.2075.8: 14.0.1000.169 - 14.0.2075.8, KB 5058716 - Previous SQL2017 RTM GDR: KB 5058716 - Previous SQL2017 RTM GDR, 5063761: 5063761, Security update for SQL 2016 Azure Connect Feature Pack: Security update for SQL 2016 Azure Connect Feature Pack, 13.0.7060.1: 13.0.7060.1, 13.0.7000.253 - 13.0.7055.9: 13.0.7000.253 - 13.0.7055.9, KB 5058717 - Previous SQL2016 Azure Connect Feature Pack GDR: KB 5058717 - Previous SQL2016 Azure Connect Feature Pack GDR, 5063762: 5063762, Security update for SQL Server 2016 SP3 RTM+GDR: Security update for SQL Server 2016 SP3 RTM+GDR, 13.0.6465.1: 13.0.6465.1, 13.0.6300.2 - 13.0.6460.7: 13.0.6300.2 - 13.0.6460.7, KB 5058718 - Previous SQL2016 RTM GDR: KB 5058718 - 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 choose 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.2080.1 — https://support.microsoft.com/help/5063760
15.0.2140.1 — https://support.microsoft.com/help/5063758
13.0.6465.1 — https://support.microsoft.com/help/5063762
13.0.7060.1 — https://support.microsoft.com/help/5063761
14.0.3500.1 — https://support.microsoft.com/help/5063759
16.0.1145.1 — https://support.microsoft.com/help/5063756
16.0.4210.1 — https://support.microsoft.com/help/5063814
15.0.4440.1 — https://support.microsoft.com/help/5063757