Microsoft SQL Server Remote Code Execution Vulnerability

CVE-2019-1068
Security Vulnerability

Released: Jul 9, 2019

Last updated: Dec 3, 2019

Assigning CNA
Microsoft
CVE.org link
CVE-2019-1068

Executive Summary

A remote code execution vulnerability exists in Microsoft SQL Server when it incorrectly handles processing of internal functions. An attacker who successfully exploited this vulnerability could execute code in the context of the SQL Server Database Engine service account.

To exploit the vulnerability, an authenticated attacker would need to submit a specially crafted query to an affected SQL server.

The security update addresses the vulnerability by modifying how the Microsoft SQL Server Database Engine handles the processing of functions.

Exploitability

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

Publicly disclosed
Yes
Exploited
No
Exploitability assessment
Exploitation Less Likely

FAQ

There are GDR and/or CU (Cumulative Update) updates offered for my version of SQL Server. How do I know which update to use?

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…
4505217 Description of the security update for the Remote Code Execution vulnerability in SQL Server 2014 SP2 (GDR): June 11, 2019 12.0.5000.0 - 12.0.5214.6 KB4057120
4505419 Description of the security update for the Remote Code Execution vulnerability in SQL Server 2014 SP2 (CU): June 11, 2019 12.0.5511.0 - 12.0.5632.1 KB4491540 – SQL14 SP2 CU17
4505218 Description of the security update for the Remote Code Execution vulnerability in SQL Server 2014 SP3 (GDR): June 11, 2019 12.0.6024.0 SP3
4505422 Description of the security update for the Remote Code Execution vulnerability in SQL Server 2014 SP3 (CU): June 11, 2019 12.0.6205.1 - 12.0.6259.0 KB4491539 – SQL14 SP3 CU3
4505219 Description of the security update for the Remote Code Execution vulnerability in SQL Server 2016 SP1(GDR): June 11, 2019 13.0.4001.0 - 13.0.4224.16 KB4458842
4505221 Description of the security update for the Remote Code Execution vulnerability in SQL Server 2016 SP1 (CU): June 11, 2019 13.0.4411.0 - 13.0.4574.0 KB4495257 – SQL16 SP1 CU15
4505220 Description of the security update for the Remote Code Execution vulnerability in SQL Server 2016 SP2 (GDR): June 11, 2019 13.0.5026.0 - 13.0.5081.1 KB4293802
4505222 Description of the security update for the Remote Code Execution vulnerability in SQL Server 2016 SP2 (CU): June 11, 2019 13.0.5149.0 - 13.0.5337.0 KB4495256 – SQL SP2 CU7
4505224 Description of the security update for the Remote Code Execution vulnerability in SQL Server 2017 (GDR): June 11, 2019 14.0.1000.169 - 14.0.2014.14 KB4494351
4505225 Description of the security update for the Remote Code Execution vulnerability in SQL Server 2017 (CU): June 11, 2019 14.0.3006.16 - 14.0.3162.1 KB4498951 – SQL17 RTM CU15

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 chose 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.

Does this security update apply to SQL Server 2017 on Linux or on Linux Docker Containers?

Yes. For information on obtaining and installing the CU or GDR updates on Linux Operating Systems or Docker Containers, please see:

  1. Configure repositories for installing and upgrading SQL Server on Linux
  2. Release notes for SQL Server 2017 on Linux
  3. Official images for Microsoft SQL Server on Linux for Docker Engine

Will these security updates be offered to SQL Server clusters?

Yes. The updates will also be offered to SQL Server 2016 SP1/SP2 and SQL Server 2017 RTM instances that are clustered. Updates for SQL Server clusters will require user interaction. If the SQL Server 2016 SP1/SP2 or SQL Server 2017 RTM cluster has a passive node, to reduce downtime, Microsoft recommends that you scan and apply the update to the inactive node first, then scan and apply it to the active node. When all components have been updated on all nodes, the update will no longer be offered.

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.

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
All results loaded
Loaded all 14 rows

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?