Code execution via undisclosed heap buffer overflow
Published Nov 12, 2024 · Updated Jul 8, 2025
A heap-based buffer overflow in Microsoft SQL Server Native Client allows remote attackers to execute code after required user interaction. Microsoft has not disclosed the specific parser, malformed field, or incorrect memory operation that triggers the overflow. Successful exploitation runs attacker-controlled code in the affected client's security context, and no authentication to the malicious endpoint is required.
Summary
What happened
A heap-based buffer overflow in Microsoft SQL Server Native Client allows remote attackers to execute code after required user interaction. Microsoft has not disclosed the specific parser, malformed field, or incorrect memory operation that triggers the overflow. Successful exploitation runs attacker-controlled code in the affected client's security context, and no authentication to the malicious endpoint is required.
The record
- CVE
- CVE-2024-48999
- Published
- Nov 12, 2024
- Updated
- Jul 8, 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
- Nov 12, 2024CVE publishedPublication date reported by the CVE source.
- Jul 8, 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.7050.2
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