Security readout for executives and security teams
Plain-English summary
CVE-2024-21360 is a high-severity remote code execution flaw in Microsoft's WDAC OLE DB provider for SQL Server. Successful exploitation could let an attacker compromise confidentiality, integrity, and availability on an affected Windows system. The CVSS assessment indicates user interaction is required, reducing—but not removing—the risk.
Executive priority
Treat as a high-priority patching item because successful exploitation can enable remote code execution with broad system impact. Prioritize affected, user-facing, and business-critical systems. The required user interaction provides some constraint, while the absence of supplied active-exploitation evidence does not justify deferral.
Technical view
The vulnerability is classified as CWE-122, a heap-based buffer overflow, with CVSS 3.1 score 8.8. Its vector indicates network reachability, low attack complexity, no required privileges, required user interaction, unchanged scope, and high impact across confidentiality, integrity, and availability. The supplied sources do not describe the triggering mechanism.
Likely exposure
Exposure applies to listed Windows 10, Windows 11, and Windows Server releases containing the affected WDAC OLE DB provider. Prioritize systems using SQL Server connectivity workflows and confirm exact applicability through Microsoft's advisory. The supplied affected list may not establish every supported build or edition.
Exploitation context
The source bundle does not provide evidence of active exploitation, and this CVE is not identified as CISA KEV. Exploit maturity is recorded as undefined. User interaction is required, but the sources do not explain the necessary interaction or attack delivery method.
Researcher notes
The available evidence supports a heap-based buffer overflow classification and the CVSS attack conditions, but provides no technical root cause, affected component versions, proof-of-concept status, telemetry, or attack-chain details. Validate build-specific exposure and remediation exclusively against the current Microsoft advisory.
Mitigation direction
- Review Microsoft's CVE advisory and deploy the applicable security update for each affected Windows release.
- Prioritize exposed workstations and servers using OLE DB connectivity to SQL Server.
- Apply normal change controls, backups, and staged testing before broad update deployment.
- If immediate updating is impossible, obtain product-specific mitigations from Microsoft guidance.
Validation and detection
- Inventory listed Windows versions and identify systems using the affected OLE DB provider.
- Compare installed update levels against Microsoft's CVE advisory for each operating system release.
- Use authenticated vulnerability scanning or endpoint-management reporting to confirm update installation.
- Retest updated systems and investigate devices that remain vulnerable or lack reliable inventory data.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-122: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-21360 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C2.85.9microsoftVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Microsoft WDAC OLE DB provider for SQL Server Remote Code Execution VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.