CVE-2024-21411
Skype ≤ 8.113
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2024-21411 is a high-severity Insecure Default Variable Initialization (CWE-453) vulnerability in Skype Skype. Its CVSS base score is 8.8 (High).
Operationally, ranked in the top 16% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to CM-2 (Baseline Configuration) and CM-6 (Configuration Settings) — 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-21411 is a remote code execution vulnerability in Skype for Consumer that carries a CVSS 3.1 score of 8.8. The flaw is tracked under CWE-453 and was published on 12 March 2024.
An unauthenticated attacker can exploit the issue over the network with low complexity and only user interaction required, resulting in full impact to confidentiality, integrity, and availability on the affected system.
Microsoft publishes mitigation guidance for the vulnerability in its Security Response Center advisory at the listed reference URL. The current EPSS score stands at 0.0504 with an identical peak value, indicating no material rise in observed exploitation interest after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-19120
Vulnerability Data
Skype for Consumer Remote Code Execution Vulnerability
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 4 hardening rules · 2 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Requires establishing the most restrictive configuration settings, which directly overrides or prevents use of insecure default variable initializations.
Requires maintaining a documented baseline configuration that can enforce secure initial values instead of insecure defaults.
Mandates application of security engineering principles during development that include use of secure defaults and proper variable initialization.
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.
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 can detect insecure defaults but does not prevent them.
Configuration management enforces secure default values and prevents insecure initialization.
Secure development life cycle requires explicit secure initialization of variables.
Secure architecture principles include avoiding insecure defaults in design.
Secure coding standards mandate explicit, safe variable initialization.