Описание
Microsoft SQL Server Remote Code Execution Vulnerability
A buffer overflow vulnerability exists in the Microsoft SQL Server that could allow remote code execution on an affected system. 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 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 objects in memory.
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?
- 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… |
|---|---|---|---|
| 4293803 | Description of the security update for the Remote Code Execution vulnerability in SQL Server 2017 (GDR): August 14, 2018 | 14.0.1000.169 - 14.0.2000.63 | 4057122 |
| 4293805 | Description of the security update for the Remote Code Execution vulnerability in SQL Server 2017 (CU): August 14, 2018 | 14.0.3006.16 - 14.0.3030.27 | KB4341265 – RTM CU9 |
| 4458842 | Description of the security update for the Remote Code Execution vulnerability in SQL Server 2016 SP1(GDR): August 14, 2018 | 13.0.4001.0 - 13.0.4223.10 | 4293801 |
| 4293808 | Description of the security update for the Remote Code Execution vulnerability in SQL Server 2016 SP1 (CU): August 14, 2018 | 13.0.4411.0 - 13.0.4514.0 | KB4341569 – SP1 CU10 |
| 4293802 | Description of the security update for the Remote Code Execution vulnerability in SQL Server 2016 SP2 (GDR): August 14, 2018 | 13.0.5026.0 - 13.0.5099.0 | SP2 |
| 4458621 | Description of the security update for the Remote Code Execution vulnerability in SQL Server 2016 SP2 (CU): August 14, 2018 | 13.0.5149.0 - 13.0.5161.0 | KB4293807 – SP2 CU2-GDR |
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 update servicing branches in place for SQL Server. The primary difference between the two is that CU branches cumulatively include all updates for a given baseline, while GDR branches include only cumulative critical updates for a given baseline. A baseline can be the initial RTM release or a Service Pack.
For any given baseline, either the GDR or CU updates are options if you are a) at the baseline version (never installed any servicing updates, CU or GDR), or b) have only installed GDR updates. The CU update is the only option if you have installed a previous SQL Server CU for the baseline you are on.
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:
- Configure repositories for installing and upgrading SQL Server on Linux
- Release notes for SQL Server 2017 on Linux
- 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.
Обновления
| Продукт | Статья | Обновление |
|---|---|---|
| Microsoft SQL Server 2016 for x64-based Systems Service Pack 1 (GDR) | ||
| Microsoft SQL Server 2016 for x64-based Systems Service Pack 1 (CU) | ||
| Microsoft SQL Server 2017 for x64-based Systems (GDR) | ||
| Microsoft SQL Server 2017 for x64-based Systems (CU) | ||
| Microsoft SQL Server 2016 for x64-based Systems Service Pack 2 (CU) | ||
| Microsoft SQL Server 2016 for x64-based Systems Service Pack 2 (GDR) |
Показывать по
Возможность эксплуатации
Publicly Disclosed
Exploited
Latest Software Release
Older Software Release
DOS
EPSS
Связанные уязвимости
A buffer overflow vulnerability exists in the Microsoft SQL Server that could allow remote code execution on an affected system, aka "Microsoft SQL Server Remote Code Execution Vulnerability." This affects Microsoft SQL Server.
A buffer overflow vulnerability exists in the Microsoft SQL Server that could allow remote code execution on an affected system, aka "Microsoft SQL Server Remote Code Execution Vulnerability." This affects Microsoft SQL Server.
Уязвимость системы управления базами данных SQL Server, вызванная переполнением буфера, позволяющая нарушителю выполнить произвольный код
EPSS