A recent vulnerability was discovered, related to column store indexes, that could allow an attacker to exploit a system. The attacker needs to be authenticated first and also prepare the environment, which makes it a bit unlikely to happen, IMHO, but you never know.
Ranges from SQL Server 2014 all the way up to SQL Server 2019!
The below table has been brought in from the source URL and enriched with downloadable links for your ease.
|Update number||Title||Apply if current product version is…||This security update also includes servicing releases up through…|
|5014356||Security update for SQL Server 2019 RTM GDR: June 14, 2022||15.0.2000.5 – 15.0.2080.9||KB 4583458 – Previous SQL19 RTM GDR|
|5014353||Security update for SQL Server 2019 RTM CU16: June 14, 2022||15.0.4003.23 – 15.0.4223.1||KB 5011644 – SQL19 RTM CU16|
|5014354||Security update for SQL Server 2017 RTM GDR: June 14, 2022||14.0.1000.169 – 14.0.2037.2||KB4583456 – Previous SQL17 RTM GDR|
|5014553||Security update for SQL Server 2017 RTM CU29: June 14, 2022||14.0.3006.16 – 14.0.3436.1||KB5010786 – SQL17 RTM CU29|
|5014365||Security update for SQL Server 2016 Service Pack 2 (GDR): June 14, 2022||13.0.5026.0 – 13.0.5103.6||KB4583460 – Previous SQL16 SP2 GDR|
|5014351||Security update for SQL Server 2016 Service Pack 2 CU17: June 14, 2022||13.0.5149.0 – 13.0.5888.11||KB5001092 – SQL SP2 CU17|
|5014355||Security update for SQL Server 2016 Service Pack 3 (GDR): June 14, 2022||13.0.6300.2||N/A|
|5015371||Security update for SQL Server 2016 Service Pack 3 Azure Connectivity Pack: June 14, 2022||13.0.7000.253||N/A|
|5014165||Security update for SQL Server 2014 Service Pack 3 (GDR): June 14, 2022||12.0.6024.0 – 12.0.6164.21||KB4583463 – Previous SQL14 SP3 GDR|
|5014164||Security update for SQL Server 2014 Service Pack 3 CU4: June 14, 2022||12.0.6205.1 – 12.0.6433.1||KB4583462 – SQL14 SP3 CU4|
As always, test before applying to production.