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.

According to the CVSS metric, user interaction is required (UI:R). What interaction would the user have to do?
An attacker could exploit the vulnerability by tricking an authenticated user (CVSS metric UI:R) into attempting to connect to a malicious SQL server via a connection driver (for example: ODBC and / or OLEDB as applicable).

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 ODBC Driver 17 or 18 for SQL Server. 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 ODBC Driver 17 or 18 for SQL Server. 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.
5029503: 5029503, Security update for SQL Server 2022 CU8+GDR: Security update for SQL Server 2022 CU8+GDR, 16.0.4003.1 - 16.0.4075.1: 16.0.4003.1 - 16.0.4075.1, KB 5029666 - SQL2022 RTM CU8: KB 5029666 - SQL2022 RTM CU8, 5029379: 5029379, Security update for SQL Server 2022 RTM+GDR: Security update for SQL Server 2022 RTM+GDR, 16.0.1000.6 - 16.0.1050.5: 16.0.1000.6 - 16.0.1050.5, KB 5021522 - Previous SQL2022 RTM GDR: KB 5021522 - Previous SQL2022 RTM GDR, 5029378: 5029378, Security update for SQL Server 2019 CU22+GDR: Security update for SQL Server 2019 CU22+GDR, 15.0.4003.23 - 15.0.4322.2: 15.0.4003.23 - 15.0.4322.2, KB 5027702 - SQL2019 RTM CU22: KB 5027702 - SQL2019 RTM CU22, 5029377: 5029377, Security update for SQL Server 2019 RTM+GDR: Security update for SQL Server 2019 RTM+GDR, 15.0.2000.5 - 15.0.2101.7: 15.0.2000.5 - 15.0.2101.7, KB 5021125 - Previous SQL2019 RTM GDR: KB 5021125 - Previous SQL2019 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 into attempting to connect to a malicious SQL server via ODBC, which could result in the client receiving a malicious networking packet. This could allow the attacker to execute code remotely on the client.

Security updates
15.0.2104.1 — https://support.microsoft.com/help/5029377
16.0.1105.1 — https://support.microsoft.com/help/5029379
17.10.5.1 — https://learn.microsoft.com/sql/connect/odbc/windows/release-notes-odbc-sql-server-windows#17105
17.10.5.1 — https://learn.microsoft.com/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server#18
17.10.5.1 — https://learn.microsoft.com/sql/connect/odbc/linux-mac/install-microsoft-odbc-driver-sql-server-macos#17
18.3.2.1 — https://learn.microsoft.com/sql/connect/odbc/windows/release-notes-odbc-sql-server-windows#1832
16.0.4080.1 — https://support.microsoft.com/help/5029503
15.0.4326.1 — https://support.microsoft.com/help/5029378