CVE-2024-49117
Microsoft Windows 11 22H2 ≤ 10.0.22621.4602
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2024-49117 is a high-severity Return of Wrong Status Code (CWE-393) vulnerability in Microsoft Windows 11 22H2. Its CVSS base score is 8.8 (High).
Operationally, ranked in the top 40% 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 SI-6 (Security and Privacy Function Verification) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-43758
Vulnerability Data
Windows Hyper-V Remote Code Execution Vulnerability
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation at post-design stages directly exercises code paths and can identify functions returning incorrect status codes.
Verification of correct security/privacy function operation will surface incorrect status codes that alter expected behavior.
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 such as code review, unit testing, and static analysis directly prevent incorrect status codes from being returned.
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 functions returning wrong status codes.
Secure development lifecycle includes code review and testing that can catch incorrect status codes.
Secure coding standards directly address proper return-value handling and error indication.