Remote code execution via OLE DB heap overflow
Published Jul 9, 2024 · Updated Dec 9, 2025
Heap-based buffer overflow in Microsoft SQL Server Native Client OLE DB Provider allows remote attackers to execute code through a malicious SQL server. Microsoft identifies the overflow in the provider but has not disclosed the affected parser, field, or precise out-of-bounds write operation. Exploitation requires an authenticated user to initiate an OLE DB connection to an attacker-controlled database, after which code runs in that user's context.
Summary
What happened
Heap-based buffer overflow in Microsoft SQL Server Native Client OLE DB Provider allows remote attackers to execute code through a malicious SQL server. Microsoft identifies the overflow in the provider but has not disclosed the affected parser, field, or precise out-of-bounds write operation. Exploitation requires an authenticated user to initiate an OLE DB connection to an attacker-controlled database, after which code runs in that user's context.
The record
- CVE
- CVE-2024-37321
- Published
- Jul 9, 2024
- Updated
- Dec 9, 2025
- Vendor
- Microsoft
- Product
- Microsoft SQL Server 2016 Service Pack 3 Azure Connect Feature Pack
- Classifications
- CWE-122, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 9, 2024CVE publishedPublication date reported by the CVE source.
- Dec 9, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=13.0.0 <13.0.7037.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo