Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2024-38087 is a high-severity Double Free (CWE-415) vulnerability in Microsoft Sql Server 2016. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked in the top 25% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-38087 is a remote code execution vulnerability in the SQL Server Native Client OLE DB Provider. The flaw carries a CVSS 3.1 score of 8.8 and is associated with CWE-415 (double-free). It affects Microsoft SQL Server Native Client installations that expose the OLE DB interface to untrusted input.
An unauthenticated remote attacker can trigger the issue by supplying a malicious OLE DB connection string or query response that the provider processes. Successful exploitation grants the attacker the ability to execute arbitrary code with the privileges of the affected process, potentially leading to full system compromise, data exfiltration, or persistence.
Microsoft’s advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-38087 recommends applying the security updates released on July 9, 2024, which address the double-free condition in supported versions of SQL Server Native Client. Administrators are advised to install the patches promptly and to restrict exposure of OLE DB endpoints where feasible.
The associated EPSS score has remained flat at 0.0718 with no material increase since disclosure, indicating limited observed exploitation interest to date.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-37777
Vulnerability Data
SQL Server Native Client OLE DB Provider Remote Code Execution Vulnerability
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 1 hardening rule · 1 OS baseline
—
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation explicitly includes dynamic analysis and fuzzing that locate double-free defects before release.
Security engineering principles can require memory-safe allocation patterns or language features that structurally eliminate double-free opportunities.
Flaw remediation processes require identification and correction of memory-management defects such as double free once discovered.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent double-free errors via static analysis, safe memory APIs, and testing.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect double-free conditions before release.
Secure development life cycle includes memory-safety practices that can prevent double-free bugs.
Application security requirements can mandate memory-safety rules that reduce double-free risk.
Secure system architecture and engineering principles can prescribe safe memory-management patterns.
Secure coding standards directly address proper use of free() and similar functions.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248590 OL 8 must clear the page allocator to prevent use-after-free attacks. prevents CWE-415