Summary
Impact: Remote Code Execution. Microsoft rating: Important. Not known to be exploited — Exploitation Less Likely. Customer action: Required.
Details
How could an attacker exploit this vulnerability?
An authenticated attacker could exploit the vulnerability by executing a specially crafted query using $ partition against a table with a Column Store index.
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.
5014356: 5014356, Security update for SQL Server 2019 RTM GDR: June 14, 2022: Security update for SQL Server 2019 RTM GDR: June 14, 2022, 15.0.2000.5 - 15.0.2080.9: 15.0.2000.5 - 15.0.2080.9, KB 4583458 - Previous SQL19 RTM GDR: KB 4583458 - Previous SQL19 RTM GDR, 5014353: 5014353, Security update for SQL Server 2019 RTM CU16: June 14, 2022: Security update for SQL Server 2019 RTM CU16: June 14, 2022, 15.0.4003.23 - 15.0.4223.1: 15.0.4003.23 - 15.0.4223.1, KB 5011644 – SQL19 RTM CU16: KB 5011644 – SQL19 RTM CU16, 5014354: 5014354, Security update for SQL Server 2017 RTM GDR: June 14, 2022: Security update for SQL Server 2017 RTM GDR: June 14, 2022, 14.0.1000.169 - 14.0.2037.2: 14.0.1000.169 - 14.0.2037.2, KB4583456 - Previous SQL17 RTM GDR: KB4583456 - Previous SQL17 RTM GDR, 5014553: 5014553, Security update for SQL Server 2017 RTM CU29: June 14, 2022: Security update for SQL Server 2017 RTM CU29: June 14, 2022, 14.0.3006.16 - 14.0.3436.1: 14.0.3006.16 - 14.0.3436.1, KB5010786 – SQL17 RTM CU29: KB5010786 – SQL17 RTM CU29, 5014365: 5014365, Security update for SQL Server 2016 Service Pack 2 (GDR): June 14, 2022: Security update for SQL Server 2016 Service Pack 2 (GDR): June 14, 2022, 13.0.5026.0 - 13.0.5103.6: 13.0.5026.0 - 13.0.5103.6, KB4583460 - Previous SQL16 SP2 GDR: KB4583460 - Previous SQL16 SP2 GDR, 5014351: 5014351, Security update for SQL Server 2016 Service Pack 2 CU17: June 14, 2022: Security update for SQL Server 2016 Service Pack 2 CU17: June 14, 2022, 13.0.5149.0 - 13.0.5888.11: 13.0.5149.0 - 13.0.5888.11, KB5001092 – SQL SP2 CU17: KB5001092 – SQL SP2 CU17, 5014355: 5014355, Security update for SQL Server 2016 Service Pack 3 (GDR): June 14, 2022: Security update for SQL Server 2016 Service Pack 3 (GDR): June 14, 2022, 13.0.6300.2: 13.0.6300.2, N/A: N/A, 5015371: 5015371, Security update for SQL Server 2016 Service Pack 3 Azure Connectivity Pack: June 14, 2022: Security update for SQL Server 2016 Service Pack 3 Azure Connectivity Pack: June 14, 2022, 13.0.7000.253: 13.0.7000.253, N/A: N/A, 5014165: 5014165, Security update for SQL Server 2014 Service Pack 3 (GDR): June 14, 2022: Security update for SQL Server 2014 Service Pack 3 (GDR): June 14, 2022, 12.0.6024.0 - 12.0.6164.21: 12.0.6024.0 - 12.0.6164.21, KB4583463 - Previous SQL14 SP3 GDR: KB4583463 - Previous SQL14 SP3 GDR, 5014164: 5014164, Security update for SQL Server 2014 Service Pack 3 CU4: June 14, 2022: Security update for SQL Server 2014 Service Pack 3 CU4: June 14, 2022, 12.0.6205.1 - 12.0.6433.1: 12.0.6205.1 - 12.0.6433.1, KB4583462 – SQL14 SP3 CU4: KB4583462 – SQL14 SP3 CU4
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.
According to the CVSS metric, the attack complexity is high (AC:H). What does that mean for this vulnerability?
Successful exploitation of this vulnerability requires an attacker to take additional actions prior to exploitation to prepare the target environment.
Security updates
14.0.2042.3 — https://support.microsoft.com/help/5014354
12.0.6169.19 — https://support.microsoft.com/help/5014165
13.0.5108.50 — https://support.microsoft.com/help/5014365
12.0.6439.10 — https://support.microsoft.com/help/5014164
15.0.2095.3 — https://support.microsoft.com/help/5014356
15.0.4236.7 — https://support.microsoft.com/help/5014353
14.0.3445.2 — https://support.microsoft.com/help/5014553
13.0.5893.48 — https://support.microsoft.com/help/5014351
13.0.6419.1 — https://support.microsoft.com/help/5014355
13.0.7016.1 — https://support.microsoft.com/help/5015371
Vulnerabilities 1
-
High 7.5
Microsoft SQL Server Remote Code Execution Vulnerability
Microsoft SQL Server Remote Code Execution Vulnerability
Revision history
-
#1
Information published.
References
-
CVE-2022-29143 Microsoft SQL Server Remote Code Execution Vulnerability - HTML
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2022-29143
-
Microsoft Exploitability Index
https://www.microsoft.com/en-us/msrc/exploitability-index?rtc=1
-
Microsoft Support Lifecycle
https://support.microsoft.com/lifecycle
-
Common Vulnerability Scoring System
https://www.first.org/cvss