Microsoft SQL Server Elevation of Privilege Vulnerability

CVE-2024-37341

Security Vulnerability

Released: Sep 10, 2024

Last updated: Oct 8, 2024

Assigning CNA: Microsoft

CVE.org link: CVE-2024-37341

Impact: Elevation of Privilege

Max Severity: Important

Weakness: CWE-284: Improper Access Control

CVSS Source: Microsoft

Vector String: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Metrics: CVSS:3.1 8.8 / 7.7

Metric

Value

Base score metrics(8)

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible. The Base Score increases the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable component.

Network

The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability. Such conditions may require the collection of more information about the target or computational exceptions. The assessment of this metric excludes any requirements for user interaction in order to exploit the vulnerability. If a specific configuration is required for an attack to succeed, the Base metrics should be scored assuming the vulnerable component is in that configuration.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

Low

The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.

User Interaction

This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise the vulnerable component. This metric determines whether the vulnerability can be exploited solely at the will of the attacker, or whether a separate user (or user-initiated process) must participate in some manner.

None

The vulnerable system can be exploited without any interaction from any user.

Scope

Does a successful attack impact a component other than the vulnerable component? If so, the Base Score increases and the Confidentiality, Integrity and Authentication metrics should be scored relative to the impacted component.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Confidentiality

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.

High

There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.

Integrity

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

High

There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.

Availability

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability. It refers to the loss of availability of the impacted component itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of an impacted component.

High

There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Temporal score metrics(3)

Exploit Code Maturity

This metric measures the likelihood of the vulnerability being attacked, and is typically based on the current state of exploit techniques, public availability of exploit code, or active, 'in-the-wild' exploitation.

Unproven

No publicly available exploit code is available, or an exploit is theoretical.

Remediation Level

The Remediation Level of a vulnerability is an important factor for prioritization. The typical vulnerability is unpatched when initially published. Workarounds or hotfixes may offer interim remediation until an official patch or upgrade is issued. Each of these respective stages adjusts the temporal score downwards, reflecting the decreasing urgency as remediation becomes final.

Official Fix

A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.

Report Confidence

This metric measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details. Sometimes only the existence of vulnerabilities are publicized, but without specific details. For example, an impact may be recognized as undesirable, but the root cause may not be known. The vulnerability may later be corroborated by research which suggests where the vulnerability may lie, though the research may not be certain. Finally, a vulnerability may be confirmed through acknowledgement by the author or vendor of the affected technology. The urgency of a vulnerability is higher when a vulnerability is known to exist with certainty. This metric also suggests the level of technical knowledge available to would-be attackers.

Confirmed

Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

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

Where can I find more information about the known functional issues that occur in the Change Data Capture (CDC) feature and that were introduced in the September 2024 GDR?

The known functional issues are addressed by the October 2024 GDR updates listed in the Security Updates table. For more information about the known issue, including workarounds, refer to the following links for the September GDR Knowledge Base articles, based on the SQL Server version you have installed:

What privileges could be gained by an attacker who successfully exploited the vulnerability?

An attacker who successfully exploited this vulnerability could gain administrator privileges.

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…
5046059	Security update for SQL Server 2022 CU15+GDR	16.0.4003.1 - 16.0.4145.4	KB 5041321 - SQL2022 RTM CU15
5046057	Security update for SQL Server 2022 RTM+GDR	16.0.1000.6 - 16.0.1125.1	KB 5042211 - SQL2022 RTM GDR
5046060	Security update for SQL Server 2019 CU28+GDR	15.0.4003.23 - 15.0.4390.2	KB 5042749 - SQL2019 RTM CU28 GDR
5046056	Security update for SQL Server 2019 RTM+GDR	15.0.2000.5 - 15.0.2120.1	KB 5042214 - SQL2019 RTM GDR
5046061	Security update for SQL Server 2017 CU31+GDR	14.0.3006.16 - 14.0.3475.1	KB 5040940 - SQL2017 RTM CU31
5046058	Security update for SQL Server 2017 RTM+GDR	14.0.1000.169 - 14.0.2060.1	KB 5042217 - SQL2017 RTM GDR
5046062	Security update for SQL 2016 Azure Connect Feature Pack	13.0.7000.253 - 13.0.7040.1	KB 5042209 - SQL2016 Azure Connect Feature Pack GDR
5046063	Security update for SQL Server 2016 SP3 RTM+GDR	13.0.6300.2 - 13.0.6445.1	KB 5042207 - 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.

Acknowledgements

Anonymous

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

Release date

Product

Platform

Impact

Max Severity

Article

Download

Build Number

Sep 10, 2024

Microsoft SQL Server 2022 for x64-based Systems (CU 15)

Elevation of Privilege

Important

5046059

Security Update

16.0.4150.1

Sep 10, 2024

Microsoft SQL Server 2019 for x64-based Systems (CU 28)

Elevation of Privilege

Important

5046060

Security Update

15.0.4395.2

Sep 10, 2024

Microsoft SQL Server 2022 for x64-based Systems (GDR)

Elevation of Privilege

Important

5046057

Security Update

16.0.1130.5

Sep 10, 2024

Microsoft SQL Server 2017 for x64-based Systems (CU 31)

Elevation of Privilege

Important

5046061

Security Update

14.0.3480.1

Sep 10, 2024

Microsoft SQL Server 2016 for x64-based Systems Service Pack 3 Azure Connect Feature Pack

Elevation of Privilege

Important

5046062

Security Update

13.0.7045.2

Sep 10, 2024

Microsoft SQL Server 2016 for x64-based Systems Service Pack 3 (GDR)

Elevation of Privilege

Important

5046063

Security Update

13.0.6450.1

Sep 10, 2024

Microsoft SQL Server 2019 for x64-based Systems (GDR)

Elevation of Privilege

Important

5046056

Security Update

15.0.2125.1

Sep 10, 2024

Microsoft SQL Server 2017 for x64-based Systems (GDR)

Elevation of Privilege

Important

5046058

Security Update

14.0.2065.1

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

version

revisionDate

description

2.0

Oct 8, 2024

To address known functional issues that occur in the Change Data Capture (CDC) feature that were introduced in the September 2024 GDR, Microsoft has released updated GDR for the following versions of SQL Server: SQL Server 2016, SQL Server 2017, SQL Server 2019, and SQL Server 2022. For more information see the FAQ section of CVE-2024-37341.

1.0

Sep 10, 2024

Information published.

How satisfied are you with the MSRC Security Update Guide?