Cyber Resilience

CVE-2024-48997

High

Published: 12 November 2024

Published
12 November 2024
Modified
15 November 2024
KEV Added
Patch
CVSS Score v3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0403 88.7th percentile
Risk Priority 20 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2024-48997 is a high-severity Heap-based Buffer Overflow (CWE-122) vulnerability in Microsoft Sql Server 2016. Its CVSS base score is 8.8 (High).

Operationally, ranked in the top 11.3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

Deeper analysis

CVE-2024-48997 is a remote code execution vulnerability in the SQL Server Native Client component, assigned a CVSS v3.1 base score of 8.8 and also tagged under CWE-122. The flaw affects Microsoft SQL Server client software that processes untrusted input over the network.

An unauthenticated attacker can trigger the issue remotely with low attack complexity and only user interaction required, resulting in full compromise of confidentiality, integrity, and availability on the affected system.

The Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-48997 provides official guidance on available security updates and mitigation steps for supported SQL Server versions.

The associated EPSS score rose from lower values after disclosure to a peak of 0.0703 on 2025-12-11 before receding to the current 0.0403, indicating measurable post-publication exploitation interest.

EU & UK References

Vulnerability details

SQL Server Native Client Remote Code Execution Vulnerability

CWE(s)

Related Threats

No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.

Affected Assets

microsoft
sql server 2016
13.0.6300.2 — 13.0.6455.2 · 13.0.7000.253 — 13.0.7050.2
microsoft
sql server 2017
14.0.1000.169 — 14.0.2070.1 · 14.0.3006.16 — 14.0.3485.1
microsoft
sql server 2019
15.0.2000.5 — 15.0.2130.3 · 15.0.4003.23 — 15.0.4410.1

Mitigating Controls

No mitigating controls mapped yet. The per-CVE control annotator has not reached this CVE.

References