Security readout for executives and security teams
Plain-English summary
This high-severity Windows vulnerability could let an attacker run code after a user interacts with malicious content handled by the affected WDAC OLE DB provider for SQL Server. Successful exploitation could compromise data, system integrity, and availability. The supplied sources identify affected Windows client and server releases and reference a Microsoft security update.
Executive priority
Treat as a high-priority patching issue, especially on business-critical servers and endpoints processing untrusted content. Establish exposure promptly and deploy Microsoft’s applicable updates through normal change controls. Escalate unsupported or unpatchable systems for documented compensating controls and replacement planning.
Technical view
CVE-2024-21367 is a remote code execution vulnerability classified as CWE-122, an out-of-bounds heap write. Its CVSS 3.1 score is 8.8: network-accessible, low complexity, no privileges required, but user interaction is required. Successful exploitation affects confidentiality, integrity, and availability without changing security scope.
Likely exposure
Exposure is most likely on listed Windows 10, Windows 11, and Windows Server systems using the affected WDAC OLE DB provider. The bundle does not establish whether every listed installation is exploitable by default. Confirm exact products, builds, provider usage, and applicable updates against Microsoft’s advisory.
Exploitation context
The supplied record does not identify this CVE as being in CISA KEV, and its CVSS vector marks exploit maturity as unproven. No cited source in the bundle establishes active exploitation. User interaction is required, which reduces opportunistic risk but does not prevent targeted exploitation.
Researcher notes
The source bundle supplies the CVSS vector, CWE classification, affected-product rows, and Microsoft advisory, but no detailed attack path or confirmed exploitation evidence. Some affected entries contain duplicate or inconsistent product labels, so researchers should use Microsoft’s advisory as the authority for exact applicability and update mapping.
Mitigation direction
- Apply the applicable Microsoft security update for each affected Windows release.
- Check Microsoft guidance for release-specific prerequisites, servicing requirements, or mitigations.
- Prioritize systems that use the affected provider or process externally supplied content.
- Use compensating controls only when Microsoft documents them for this vulnerability.
Validation and detection
- Inventory the listed Windows client and server versions and their build levels.
- Determine where the WDAC OLE DB provider for SQL Server is installed or used.
- Verify applicable Microsoft security updates are installed successfully on each exposed system.
- Re-scan patched systems and review update failures or unsupported operating systems.
Public sources used
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-21367 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.