Code execution through undisclosed input validation flaw
Published Apr 11, 2023 · Updated Feb 28, 2025
Improper input validation in Microsoft ODBC and OLE DB drivers allows local attackers to execute code after required user interaction. Microsoft has not published the malformed input, parsing locus, or validation operation that triggers the flaw. Exploitation requires user interaction and executes code in the affected client process, exposing the data and privileges available to that process.
Summary
What happened
Improper input validation in Microsoft ODBC and OLE DB drivers allows local attackers to execute code after required user interaction. Microsoft has not published the malformed input, parsing locus, or validation operation that triggers the flaw. Exploitation requires user interaction and executes code in the affected client process, exposing the data and privileges available to that process.
The record
- CVE
- CVE-2023-28304
- Published
- Apr 11, 2023
- Updated
- Feb 28, 2025
- Vendor
- Microsoft
- Product
- Microsoft ODBC Driver 18 for SQL Server
- Classifications
- CWE-20
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 11, 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=18.0.0.0 <18.2.1.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.
Weakness, pattern, technique
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