Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability
CVE-2023-21704
Security Vulnerability
Released: Feb 14, 2023
- Assigning CNA
- Microsoft
- CVE.org link
- CVE-2023-21704
- Impact
- Remote Code Execution
- Max Severity
- Important
- Weakness
- CVSS Source
- Microsoft
- Vector String
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
- Metrics
- CVSS:3.1 7.8 / 6.8Base score metrics: 7.8 / Temporal score metrics: 6.8
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.
Local
The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document)
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
According to the CVSS metric, the attack vector is local (AV:L). Why does the CVE title indicate that this is a remote code execution?
The word Remote in the title refers to the location of the attacker. This type of exploit is sometimes referred to as Arbitrary Code Execution (ACE). The attack itself is carried out locally. This means an attacker or victim needs to execute code from the local machine to exploit the 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… |
|---|---|---|---|
| 5021522 | Security update for SQL Server 2022 RTM+GDR (Feb 2023) | 16.0.1000.6 | N/A |
| 5021124 | Security update for SQL Server 2019 CU18+GDR (Feb 2023) | 15.0.4003.23 - 15.0.4261.1 | KB 5017593 – SQL2019 RTM CU18 |
| 5021125 | Security update for SQL Server 2019 RTM+GDR (Feb 2023) | 15.0.2000.5 - 15.0.2095.3 | KB 5014356 - Previous SQL2019 RTM GDR |
| 5021126 | Security update for SQL Server 2017 CU31+GDR (Feb 2023) | 14.0.3006.16 - 14.0.3456.2 | KB 5016884 – SQL2017 RTM CU31 |
| 5021127 | Security update for SQL Server 2017 RTM+GDR (Feb 2023) | 14.0.1000.169 - 14.0.2042.3 | KB 5014354 - Previous SQL2017 RTM GDR |
| 5021128 | Security update for SQL Server 2016 SP3 Azure Connect Feature Pack+GDR (Feb 2023) | 13.0.7000.253 - 13.0.7016.1 | KB 5015371 - Previous Azure Connect Feature Pack GDR |
| 5021129 | Security update for SQL Server 2016 SP3+GDR (Feb 2023) | 13.0.6300.2 - 13.0.6419.1 | KB 5014355 - Previous SQL2016 SP3 GDR |
| 5021045 | Security update for SQL Server 2014 SP3 CU4+GDR (Feb 2023) | 12.0.6205.1 - 12.0.6439.10 | KB 5014164 – SQL2014 SP3 CU4 |
| 5021037 | Security update for SQL Server 2014 SP3+GDR (Feb 2023) | 12.0.6024.0 - 12.0.6169.19 | KB 5014165 - Previous SQL2014 SP3 GDR |
| 5021123 | Security update for SQL Server 2012 SP4+GDR (Feb2023) | 11.0.7001.0 - 11.0.7507.2 | KB 4583465 - Previous SQL2012 SP4 GDR |
| 5021112 | Security update for SQL Server SQL2008R2 SP3+GDR (Feb2023) | 10.50.6000.34 - 10.50.6560.0 | KB 4057113 - Previous SQL2008R2 SP3 GDR |
| 5020863 | Security update for SQL Server 2008 SP4+GDR (Feb2023) | 10.00.6000.29 - 10.00.6556.0 | KB 4057114 - Previous SQL2008 SP4 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.
How could an attacker exploit this vulnerability?
An attacker could exploit the vulnerability by tricking an un-authenticated user into attempting to connect to a malicious SQL server database via ODBC. This could result in the database returning malicious data that might cause arbitrary code execution on the client.
Acknowledgements
- hexb1n
Security Updates
To determine the support lifecycle for your software, see the Microsoft Support Lifecycle.
Release date Descending
Product
Platform
Impact
Max Severity
Article
Download
Build Number
Feb 14, 2023
Microsoft SQL Server 2022 for x64-based Systems (GDR)
-
Remote Code Execution
Important
- 16.0.1050.5
Feb 14, 2023
Microsoft SQL Server 2017 for x64-based Systems (CU 31)
-
Remote Code Execution
Important
- 14.0.3460.9
Feb 14, 2023
Microsoft SQL Server 2019 for x64-based Systems (CU 18)
-
Remote Code Execution
Important
- 15.0.4280.7
Feb 14, 2023
Microsoft SQL Server 2016 for x64-based Systems Service Pack 3 Azure Connect Feature Pack
-
Remote Code Execution
Important
- 13.0.7024.30
Feb 14, 2023
Microsoft SQL Server 2016 for x64-based Systems Service Pack 3 (GDR)
-
Remote Code Execution
Important
- 13.0.6430.49
Feb 14, 2023
Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (CU 4)
-
Remote Code Execution
Important
- 12.0.6174.8
Feb 14, 2023
Microsoft SQL Server 2019 for x64-based Systems (GDR)
-
Remote Code Execution
Important
- 15.0.2101.7
Feb 14, 2023
Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (CU 4)
-
Remote Code Execution
Important
- 12.0.6174.8
Feb 14, 2023
Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (GDR)
-
Remote Code Execution
Important
- 12.0.6444.4
Feb 14, 2023
Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (GDR)
-
Remote Code Execution
Important
- 12.0.6444.4
Feb 14, 2023
Microsoft SQL Server 2017 for x64-based Systems (GDR)
-
Remote Code Execution
Important
- 14.0.2047.8
All results loaded
Loaded all 11 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
1.0
Feb 14, 2023
Information published.
How satisfied are you with the MSRC Security Update Guide?