Microsoft SQL Server Native Client OLE DB Provider heap-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.1 | $5k-$25k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Microsoft SQL Server. The impacted element is an unknown function of the component Native Client OLE DB Provider. The manipulation leads to heap-based overflow. This vulnerability is documented as CVE-2024-21414. The attack can be initiated remotely. There is not any exploit available. It is suggested to install a patch to address this issue.
Details
A vulnerability was found in Microsoft SQL Server (affected version unknown) and classified as critical. This issue affects an unknown functionality of the component Native Client OLE DB Provider. The manipulation with an unknown input leads to a heap-based overflow vulnerability. Using CWE to declare the problem leads to CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). Impacted is confidentiality, integrity, and availability. The summary by CVE is:
SQL Server Native Client OLE DB Provider Remote Code Execution Vulnerability
The weakness was released 07/09/2024 as confirmed security update guide (Website). The advisory is shared at msrc.microsoft.com. The identification of this vulnerability is CVE-2024-21414. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 02/22/2025).
The vulnerability scanner Nessus provides a plugin with the ID 216605 (Security Updates for Microsoft SQL Server (July 2024)), which helps to determine the existence of the flaw in a target environment.
Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (216605). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.microsoft.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.8VulDB Meta Temp Score: 8.1
VulDB Base Score: 8.8
VulDB Temp Score: 7.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
Vendor Base Score (Microsoft): 8.8
Vendor Vector (Microsoft): 🔍
CNA Base Score: 8.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: Heap-based overflowCWE: CWE-122 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
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 |
Nessus ID: 216605
Nessus Name: Security Updates for Microsoft SQL Server (July 2024)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Timeline
07/09/2024 🔍07/09/2024 🔍
07/09/2024 🔍
03/20/2025 🔍
Sources
Vendor: microsoft.comAdvisory: msrc.microsoft.com
Status: Confirmed
CVE: CVE-2024-21414 (🔍)
GCVE (CVE): GCVE-0-2024-21414
GCVE (VulDB): GCVE-100-270761
Entry
Created: 07/09/2024 19:24Updated: 03/20/2025 04:30
Changes: 07/09/2024 19:24 (34), 07/09/2024 19:27 (35), 01/16/2025 10:41 (13), 02/22/2025 01:48 (2), 03/20/2025 04:30 (3)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.