CVE-2024-21412
Microsoft Windows 10 1809 ≤ 10.0.17763.5458
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-21412 is a high-severity Protection Mechanism Failure (CWE-693) vulnerability in Microsoft Windows 10 1809. Its CVSS base score is 8.1 (High).
Operationally, ranked in the top 0.1% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — 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-21412 is a security feature bypass vulnerability affecting the handling of Internet Shortcut Files. The flaw carries a CVSS 3.1 score of 8.1 and is associated with CWE-693. It was publicly disclosed on 13 February 2024 and impacts components responsible for processing .url files within Microsoft environments.
An unauthenticated remote attacker can exploit the issue by supplying a malicious Internet Shortcut File over the network. Successful exploitation requires the victim to interact with the file, after which the bypass allows high-impact effects on confidentiality and integrity while leaving availability unaffected.
Microsoft’s advisory at msrc.microsoft.com details the available patches and configuration guidance, while CISA has added the CVE to its Known Exploited Vulnerabilities catalog, confirming active exploitation in the wild. The associated EPSS score remains consistently high, with a current value of 0.9377 and a peak of 0.9378.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-19121
Vulnerability Data
Internet Shortcut Files Security Feature Bypass Vulnerability
- CWE(s)
- KEV Date Added
- 13 February 2024
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
AC-3 directly requires enforcement of access authorizations via the protection mechanism itself.
AC-4 mandates use of information flow enforcement mechanisms to control data movement.
SC-2 requires separation of user and system functionality as a protection mechanism.
SC-28 requires protection mechanisms for information at rest.
SC-3 requires isolation of security functions from non-security functions.
SC-7 requires boundary protection mechanisms to monitor and control external communications.
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.
Systematic verification that security mechanisms operate according to defined standards reduces the likelihood that protection mechanisms are bypassed or disabled.
A.8.26 only requires that security requirements (including protection mechanisms) be identified and specified during development or acquisition; it does not itself mandate, implement, or enforce the mechanisms that would remove CWE-693 instances from the product.
A.8.28 mandates secure coding practices, principles, standards, design, peer review, defect removal, prohibition of insecure techniques (e.g. hard-coded passwords), and evaluation of common errors before deployment, which directly removes many instances of missing or incorrectly used protection mechanisms from first-party code; the bounded remainder is third-party components and post-deployment issues handled by other clauses (8.8, 8.29).
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.