CVE-2024-48996: SQL Server Native Client Remote Code Execution Vulnerability

I am running SQL Server on my system. What action do I need to take?

Update your relevant version of SQL Server. Any applicable driver fixes are included in those updates.

I am running my own application on my system. What action do I need to take?

Update your application to use Microsoft OLE DB Driver 18 or 19. Update the drivers to the versions listed on this page, which provide protection against this vulnerability.

I am running an application from a software vendor on my system. What action do I need to take?

Consult with your application vendor if it is compatible with Microsoft OLE DB Driver 18 or 19. Update the drivers to the versions listed in this page, which provide protection against this vulnerability

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…

5046862

Security update for SQL Server 2022 CU15+GDR

16.0.4003.1 - 16.0.4150.1

KB 5046059 - SQL2022 RTM CU15 GDR

5046861

Security update for SQL Server 2022 RTM+GDR

16.0.1000.6 - 16.0.1130.5

KB 5046057 - SQL2022 RTM GDR

5046860

Security update for SQL Server 2019 CU29+GDR

15.0.4003.23 - 15.0.4405.4

KB 5046365 - SQL2019 RTM CU29

5046859

Security update for SQL Server 2019 RTM+GDR

15.0.2000.5 - 15.0.2125.1

KB 5046056 - SQL2019 RTM GDR

5046858

Security update for SQL Server 2017 CU31+GDR

14.0.3006.16 - 14.0.3480.1

KB 5046061 - SQL2017 RTM CU31 GDR

5046857

Security update for SQL Server 2017 RTM+GDR

14.0.1000.169 - 14.0.2065.1

KB 5046058 - SQL2017 RTM GDR

5046856

Security update for SQL 2016 Azure Connect Feature Pack

13.0.7000.253 - 13.0.7045.2

KB 5046062 - SQL2016 Azure Connect Feature Pack GDR

5046855

Security update for SQL Server 2016 SP3 RTM+GDR

13.0.6300.2 - 13.0.6450.1

KB 5046063 - SQL2016 RTM 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 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.