Microsoft SQL Server Remote Code Execution Vulnerability

Security Vulnerability

Released: Jun 14, 2022

Assigning CNA
Microsoft
CVE.org link
CVE-2022-29143
Impact
Remote Code Execution
Max Severity
Important
CVSS Source
Microsoft
Vector String
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Please see Common Vulnerability Scoring System for more information on the definition of these metrics.

Exploitability

The following table provides an exploitability assessment for this vulnerability at the time of original publication.

Publicly disclosed
No
Exploited
No
Exploitability assessment
Exploitation Less Likely

FAQ

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.

Note If your SQL Server version number is not represented in the table below, your SQL Server version is no longer supported. Please upgrade to the latest Service Pack or SQL Server product in order to apply this and future security updates.

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

What are the GDR and CU update designations and how do they differ?

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.

Note: You are allowed to make a change from GDR updates to CU updates ONE TIME. Once a SQL Server CU update is applied to a SQL Server installation, there is NO way to go back to the GDR update path.

Can the security updates be applied to SQL Server instances on Windows Azure (IaaS)?

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.

Acknowledgements

Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure. See Acknowledgements for more information.

Security Updates

To determine the support lifecycle for your software, see the Microsoft Support Lifecycle.

Release date Descending

Disclaimer

The information provided in the Microsoft Knowledge Base is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

Revisions

How satisfied are you with the MSRC Security Update Guide?