CVE-2024-43502
Microsoft Windows 10 1809 ≤ 10.0.17763.6414
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:HSummary
CVE-2024-43502 is a high-severity Use of Uninitialized Resource (CWE-908) vulnerability in Microsoft Windows 10 1809. Its CVSS base score is 7.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked in the top 7% 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-43502 is an elevation of privilege vulnerability in the Windows kernel, published on October 8, 2024. It carries a CVSS 3.1 base score of 7.1 with the vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H and is associated with CWE-908. The flaw affects the Windows kernel component and enables a local attacker to obtain unauthorized access to sensitive information or disrupt system availability.
A local attacker with low privileges can exploit the issue without user interaction to achieve elevation of privilege, resulting in high confidentiality and availability impacts while leaving integrity unaffected. The EPSS score remains flat at 0.0869 with no material rise after disclosure.
Microsoft's advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-43502 supplies official mitigation guidance and patch information for affected Windows systems.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-40758
Vulnerability Data
Windows Kernel Elevation of Privilege 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 (including static analysis) can find uses of uninitialized resources after they are coded.
Requiring documented development standards and tools can mandate initialization checks and safe patterns that stop the weakness from being introduced.
Engineering principles can require explicit resource initialization before use, structurally avoiding uninitialized access.
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 activities such as static analysis and code review directly prevent use of uninitialized resources while also addressing many other weaknesses.
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 and acceptance can detect uninitialized resource usage through dynamic analysis and fuzzing.
Secure development life cycle mandates initialization checks and static analysis that can catch uninitialized resource use.
Application security requirements can specify mandatory initialization of variables and resources before use.
Secure system architecture and engineering principles include defensive coding practices that prevent use of uninitialized memory or objects.
Secure coding standards directly require explicit initialization of all variables and resources, substantially mitigating CWE-908.