Microsoft SQL Server Native Scoring Information Disclosure Vulnerability

According to the CVSS metric, privileges required is low (PR:L). What does that mean for this vulnerability?
Successful exploitation of this vulnerability requires an authenticated attacker to leverage SQL Server Native Scoring to apply pre-trained models to their data without moving it out of the database.

What type of information could be disclosed by this vulnerability?
An attacker who successfully exploited this vulnerability could potentially read small portions of heap memory.

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.
5042578: 5042578, Security update for SQL Server 2022 CU14+GDR: Security update for SQL Server 2022 CU14+GDR, 16.0.4003.1 - 16.0.4135.4: 16.0.4003.1 - 16.0.4135.4, KB 5038325 - SQL2022 RTM CU14: KB 5038325 - SQL2022 RTM CU14, 5042211: 5042211, Security update for SQL Server 2022 RTM+GDR: Security update for SQL Server 2022 RTM+GDR, 16.0.1000.6 - 16.0.1121.4: 16.0.1000.6 - 16.0.1121.4, KB 5040936 - Previous SQL2022 RTM GDR: KB 5040936 - Previous SQL2022 RTM GDR, 5042749: 5042749, Security update for SQL Server 2019 CU28+GDR: Security update for SQL Server 2019 CU28+GDR, 15.0.4003.23 - 15.0.4385.2: 15.0.4003.23 - 15.0.4385.2, KB 5039747 - SQL2019 RTM CU28: KB 5039747 - SQL2019 RTM CU28, 5042214: 5042214, Security update for SQL Server 2019 RTM+GDR: Security update for SQL Server 2019 RTM+GDR, 15.0.2000.5 - 15.0.2116.2: 15.0.2000.5 - 15.0.2116.2, KB 5040986 - Previous SQL2019 RTM GDR: KB 5040986 - Previous SQL2019 RTM GDR, 5042215: 5042215, Security update for SQL Server 2017 CU31+GDR: Security update for SQL Server 2017 CU31+GDR, 14.0.3006.16 - 14.0.3471.2: 14.0.3006.16 - 14.0.3471.2, KB 5040940 - SQL2017 RTM CU31: KB 5040940 - SQL2017 RTM CU31, 5042217: 5042217, Security update for SQL Server 2017 RTM+GDR: Security update for SQL Server 2017 RTM+GDR, 14.0.1000.169 - 14.0.2056.2: 14.0.1000.169 - 14.0.2056.2, KB 5040942 - Previous SQL2017 RTM GDR: KB 5040942 - Previous SQL2017 RTM GDR, 5042209: 5042209, Security update for SQL 2016 Azure Connect Feature Pack: Security update for SQL 2016 Azure Connect Feature Pack, 13.0.7000.253 - 13.0.7037.1: 13.0.7000.253 - 13.0.7037.1, KB 5040944 - SQL2016 Azure Connect Feature Pack: KB 5040944 - SQL2016 Azure Connect Feature Pack, 5042207: 5042207, Security update for SQL Server 2016 SP3 RTM+GDR: Security update for SQL Server 2016 SP3 RTM+GDR, 13.0.6300.2 - 13.0.6441.1: 13.0.6300.2 - 13.0.6441.1, KB 5040946 - Previous SQL2016 RTM GDR: KB 5040946 - 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.

Security updates
14.0.2060.1 — https://support.microsoft.com/help/5042217
15.0.2120.1 — https://support.microsoft.com/help/5042214
14.0.3475.1 — https://support.microsoft.com/help/5042215
16.0.1125.1 — https://support.microsoft.com/help/5042211
16.0.4140.3 — https://support.microsoft.com/help/5042578
15.0.4390.2 — https://support.microsoft.com/help/5042749