Microsoft SQL Server Reporting Services Remote Code Execution Vulnerability

CVE-2020-0618
Security Vulnerability

Released: Feb 11, 2020

Last updated: Sep 22, 2020

Assigning CNA
Microsoft
CVE.org link
CVE-2020-0618

Executive Summary

A remote code execution vulnerability exists in Microsoft SQL Server Reporting Services when it incorrectly handles page requests. An attacker who successfully exploited this vulnerability could execute code in the context of the Report Server service account.

To exploit the vulnerability, an authenticated attacker would need to submit a specially crafted page request to an affected Reporting Services instance.

The security update addresses the vulnerability by modifying how the Microsoft SQL Server Reporting Services handles page requests.

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

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…
4532097 Security update for SQL Server 2016 Service Pack 2 (GDR): Feb 11, 2020 13.0.5026.0 - 13.0.5101.9 KB4505220 - Previous SQL16 SP2 GDR
4535706 Security update for SQL Server 2016 Service Pack 2 CU11: Feb 11, 2020 13.0.5149.0 - 13.0.5598.27 KB4527378 – SQL16 SP2 CU11
4532095 Security update for SQL Server 2014 Service Pack 3 (GDR): Feb 11, 2020 12.0.6024.0 - 12.0.6108.1 KB4505218 - Previous SQL14 SP3 GDR
4535288 Security update for SQL Server 2014 Service Pack 2 CU4: Feb 11, 2020 12.0.6205.1 - 12.0.6329.1 KB4500181 – SQL14 SP3 CU4
4532098 Security update for SQL Server 2012 Service Pack 4 (QFE): Feb 11, 2020 11.0.7001.0 - 11.0.7462.6 KB4057116 – Previous SQL12 SP4 QFE

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.

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

  • Soroush Dalili (@irsdl)
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 8 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?