Remote code execution via heap buffer overflow
Published Apr 9, 2024 · Updated May 3, 2025
Heap-based buffer overflow in affected Microsoft OLE DB Driver and SQL Server builds allows remote attackers to execute arbitrary code. The published record identifies heap memory as the affected locus but does not disclose the parsed field, routine, or incorrect bounds operation. Reachability requires a user or application to connect through the affected driver; successful exploitation runs code in that client process.
Summary
What happened
Heap-based buffer overflow in affected Microsoft OLE DB Driver and SQL Server builds allows remote attackers to execute arbitrary code. The published record identifies heap memory as the affected locus but does not disclose the parsed field, routine, or incorrect bounds operation. Reachability requires a user or application to connect through the affected driver; successful exploitation runs code in that client process.
The record
- CVE
- CVE-2024-28910
- Published
- Apr 9, 2024
- Updated
- May 3, 2025
- Vendor
- Microsoft
- Product
- Microsoft SQL Server 2022
- Classifications
- CWE-122, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 9, 2024CVE publishedPublication date reported by the CVE source.
- May 3, 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.0.0 <16.0.1115.1
- Affected versionversion=16.0.0 <16.0.4120.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