CVE-2024-43474
Microsoft Sql Server 2017 14.0.1000.169 – 14.0.2060.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:LSummary
CVE-2024-43474 is a high-severity Improper Null Termination (CWE-170) vulnerability in Microsoft Sql Server 2017. Its CVSS base score is 7.6 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 33% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-43474 is an information disclosure vulnerability in Microsoft SQL Server, assigned a CVSS 3.1 score of 7.6 with the vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L. The flaw is also associated with CWE-170. It was published on 2024-09-10 and affects the database server component when accessed over a network.
An authenticated attacker with low privileges can exploit the issue remotely without user interaction to disclose sensitive information at high impact, while also producing limited integrity and availability effects on the target instance.
The Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-43474 supplies official mitigation and patch guidance for affected SQL Server versions.
The associated EPSS score has remained low, with a current value of 0.0673 and a peak of 0.0835.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-40741
Vulnerability Data
Microsoft SQL Server Information Disclosure Vulnerability
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover missing or incorrect string termination during code review or dynamic analysis.
Requiring documented development standards and tools can enforce safe string-handling practices that produce correct null termination.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly enforce correct string/array termination via coding standards, reviews, and static analysis.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect missing or incorrect null terminators before release.
Secure SDLC mandates input validation and string handling rules that prevent missing null terminators.
Application security requirements can explicitly call for proper string termination and buffer handling.
Secure architecture principles include defensive coding practices that address buffer and string termination issues.
Secure coding standards directly require correct null termination of strings and arrays.