Code execution via heap buffer overflow
Published Oct 10, 2023 · Updated Apr 14, 2025
Heap-based buffer overflow in Microsoft ODBC Driver for SQL Server allows remote attackers to execute code through a malicious server. Microsoft identifies a heap overwrite but has not disclosed the parsing routine or the malicious response field whose unchecked size corrupts memory. Exploitation requires an application user to initiate an ODBC connection to an attacker-controlled server, after which code runs in that client process.
Summary
What happened
Heap-based buffer overflow in Microsoft ODBC Driver for SQL Server allows remote attackers to execute code through a malicious server. Microsoft identifies a heap overwrite but has not disclosed the parsing routine or the malicious response field whose unchecked size corrupts memory. Exploitation requires an application user to initiate an ODBC connection to an attacker-controlled server, after which code runs in that client process.
The record
- CVE
- CVE-2023-36730
- Published
- Oct 10, 2023
- Updated
- Apr 14, 2025
- Vendor
- Microsoft
- Product
- Microsoft ODBC Driver 18 for SQL Server
- Classifications
- CWE-122, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 10, 2023CVE publishedPublication date reported by the CVE source.
- Apr 14, 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=18.0.0.0 <18.3.2.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