Code execution via malicious-server heap overflow
Published Jun 16, 2023 · Updated Feb 28, 2025
Heap-based buffer overflow in Microsoft ODBC Driver for SQL Server allows local users to execute code through a malicious server. Microsoft identifies the flaw as a heap-based buffer overflow but has not disclosed the affected parser, function, or malformed protocol field. Exploitation requires user interaction to make the client connect to an attacker-controlled SQL Server, after which crafted response data executes code in the client process.
Summary
What happened
Heap-based buffer overflow in Microsoft ODBC Driver for SQL Server allows local users to execute code through a malicious server. Microsoft identifies the flaw as a heap-based buffer overflow but has not disclosed the affected parser, function, or malformed protocol field. Exploitation requires user interaction to make the client connect to an attacker-controlled SQL Server, after which crafted response data executes code in the client process.
The record
- CVE
- CVE-2023-32025
- Published
- Jun 16, 2023
- Updated
- Feb 28, 2025
- Vendor
- Microsoft
- Product
- Microsoft Visual Studio 2019
- Classifications
- CWE-122, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 16, 2023CVE publishedPublication date reported by the CVE source.
- Feb 28, 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=16.11.0 <16.11.33
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