Microsoft SQL Server up to 2022 ODBC Driver integer underflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $5k-$25k | 0.41 |
Summary
A vulnerability was found in Microsoft SQL Server 2014 SP3/2016/2017/2019/2022. It has been classified as critical. Impacted is an unknown function of the component ODBC Driver. Performing a manipulation results in an unknown weakness. This vulnerability is known as CVE-2023-21718. Remote exploitation of the attack is possible. No exploit is available. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability classified as critical has been found in Microsoft SQL Server 2014 SP3/2016/2017/2019/2022 (Database Software). This affects an unknown code block of the component ODBC Driver. CWE is classifying the issue as CWE-191. The product subtracts one value from another, such that the result is less than the minimum allowable integer value, which produces a value that is not equal to the correct result. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Microsoft ODBC Driver for SQL Server Remote Code Execution Vulnerability
The weakness was published 02/14/2023 as confirmed security guidance (Website). It is possible to read the advisory at portal.msrc.microsoft.com. This vulnerability is uniquely identified as CVE-2023-21718. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/21/2026).
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.1VulDB Meta Temp Score: 7.4
VulDB Base Score: 8.8
VulDB Temp Score: 7.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 7.8
Vendor Vector (Microsoft): 🔍
CNA Base Score: 7.8
CNA Vector (Microsoft): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Integer underflowCWE: CWE-191 / CWE-189
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: Yes
Availability: 🔍
Status: Unproven
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
12/13/2022 🔍02/14/2023 🔍
02/14/2023 🔍
02/14/2023 🔍
08/21/2026 🔍
Sources
Vendor: microsoft.comAdvisory: portal.msrc.microsoft.com
Status: Confirmed
CVE: CVE-2023-21718 (🔍)
GCVE (CVE): GCVE-0-2023-21718
GCVE (VulDB): GCVE-100-220995
Entry
Created: 02/14/2023 20:05Updated: 08/21/2026 18:45
Changes: 02/14/2023 20:05 (26), 02/14/2023 20:06 (7), 02/14/2023 20:09 (21), 03/15/2023 14:17 (2), 03/15/2023 14:22 (11), 08/21/2026 18:45 (17)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.