Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability

According to the CVSS metric, the attack vector is local (AV:L). Why does the CVE title indicate that this is a remote code execution?
The word Remote in the title refers to the location of the attacker. This type of exploit is sometimes referred to as Arbitrary Code Execution (ACE). The attack itself is carried out locally. This means an attacker or victim needs to execute code from the local machine to exploit the vulnerability.

There are GDR and/or CU (Cumulative Update) updates offered for my version of SQL Server. How do I know which update to use?
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.
5021522: 5021522, Security update for SQL Server 2022 RTM+GDR (Feb 2023): Security update for SQL Server 2022 RTM+GDR (Feb 2023), 16.0.1000.6: 16.0.1000.6, N/A: N/A, 5021124: 5021124, Security update for SQL Server 2019 CU18+GDR (Feb 2023): Security update for SQL Server 2019 CU18+GDR (Feb 2023), 15.0.4003.23 - 15.0.4261.1: 15.0.4003.23 - 15.0.4261.1, KB 5017593 – SQL2019 RTM CU18: KB 5017593 – SQL2019 RTM CU18, 5021125: 5021125, Security update for SQL Server 2019 RTM+GDR (Feb 2023): Security update for SQL Server 2019 RTM+GDR (Feb 2023), 15.0.2000.5 - 15.0.2095.3: 15.0.2000.5 - 15.0.2095.3, KB 5014356 - Previous SQL2019 RTM GDR: KB 5014356 - Previous SQL2019 RTM GDR, 5021126: 5021126, Security update for SQL Server 2017 CU31+GDR (Feb 2023): Security update for SQL Server 2017 CU31+GDR (Feb 2023), 14.0.3006.16 - 14.0.3456.2: 14.0.3006.16 - 14.0.3456.2, KB 5016884 – SQL2017 RTM CU31: KB 5016884 – SQL2017 RTM CU31, 5021127: 5021127, Security update for SQL Server 2017 RTM+GDR (Feb 2023): Security update for SQL Server 2017 RTM+GDR (Feb 2023), 14.0.1000.169 - 14.0.2042.3: 14.0.1000.169 - 14.0.2042.3, KB 5014354 - Previous SQL2017 RTM GDR: KB 5014354 - Previous SQL2017 RTM GDR, 5021128: 5021128, Security update for SQL Server 2016 SP3 Azure Connect Feature Pack+GDR (Feb 2023): Security update for SQL Server 2016 SP3 Azure Connect Feature Pack+GDR (Feb 2023), 13.0.7000.253 - 13.0.7016.1: 13.0.7000.253 - 13.0.7016.1, KB 5015371 - Previous Azure Connect Feature Pack GDR: KB 5015371 - Previous Azure Connect Feature Pack GDR, 5021129: 5021129, Security update for SQL Server 2016 SP3+GDR (Feb 2023): Security update for SQL Server 2016 SP3+GDR (Feb 2023), 13.0.6300.2 - 13.0.6419.1: 13.0.6300.2 - 13.0.6419.1, KB 5014355 - Previous SQL2016 SP3 GDR: KB 5014355 - Previous SQL2016 SP3 GDR, 5021045: 5021045, Security update for SQL Server 2014 SP3 CU4+GDR (Feb 2023): Security update for SQL Server 2014 SP3 CU4+GDR (Feb 2023), 12.0.6205.1 - 12.0.6439.10: 12.0.6205.1 - 12.0.6439.10, KB 5014164 – SQL2014 SP3 CU4: KB 5014164 – SQL2014 SP3 CU4, 5021037: 5021037, Security update for SQL Server 2014 SP3+GDR (Feb 2023): Security update for SQL Server 2014 SP3+GDR (Feb 2023), 12.0.6024.0 - 12.0.6169.19: 12.0.6024.0 - 12.0.6169.19, KB 5014165 - Previous SQL2014 SP3 GDR: KB 5014165 - Previous SQL2014 SP3 GDR, 5021123: 5021123, Security update for SQL Server 2012 SP4+GDR (Feb2023): Security update for SQL Server 2012 SP4+GDR (Feb2023), 11.0.7001.0 - 11.0.7507.2: 11.0.7001.0 - 11.0.7507.2, KB 4583465 - Previous SQL2012 SP4 GDR: KB 4583465 - Previous SQL2012 SP4 GDR, 5021112: 5021112, Security update for SQL Server SQL2008R2 SP3+GDR (Feb2023): Security update for SQL Server SQL2008R2 SP3+GDR (Feb2023), 10.50.6000.34 - 10.50.6560.0: 10.50.6000.34 - 10.50.6560.0, KB 4057113 - Previous SQL2008R2 SP3 GDR: KB 4057113 - Previous SQL2008R2 SP3 GDR, 5020863: 5020863, Security update for SQL Server 2008 SP4+GDR (Feb2023): Security update for SQL Server 2008 SP4+GDR (Feb2023), 10.00.6000.29 - 10.00.6556.0: 10.00.6000.29 - 10.00.6556.0, KB 4057114 - Previous SQL2008 SP4 GDR: KB 4057114 - Previous SQL2008 SP4 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 un-authenticated user into attempting to connect to a malicious SQL server database via ODBC. This could result in the database returning malicious data that might cause arbitrary code execution on the client.

Security updates
14.0.2047.8 — https://support.microsoft.com/help/5021127
12.0.6444.4 — https://support.microsoft.com/help/5021037
12.0.6174.8 — https://support.microsoft.com/help/5021045
15.0.2101.7 — https://support.microsoft.com/help/5021125
13.0.6430.49 — https://support.microsoft.com/help/5021129
13.0.7024.30 — https://support.microsoft.com/help/5021128
15.0.4280.7 — https://support.microsoft.com/help/5021124
14.0.3460.9 — https://support.microsoft.com/help/5021126
16.0.1050.5 — https://support.microsoft.com/help/5021522