Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:HSummary
CVE-2025-24154 is a critical-severity Out-of-bounds Write (CWE-787) vulnerability in Apple Macos. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Downgrade Attack (T1689); ranked in the top 36% 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 SC-13 (Cryptographic Protection) — 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-2025-24154 is an out-of-bounds write vulnerability (CWE-787, CWE-757) that was addressed through improved input validation in multiple Apple operating systems. The affected software includes iOS versions prior to 18.3, iPadOS versions prior to 18.3, macOS Sequoia versions prior to 15.3, macOS Sonoma versions prior to 14.7.3, macOS Ventura versions prior to 13.7.3, and visionOS versions prior to 2.3. Published on January 27, 2025, the flaw resides at the kernel level, enabling potential memory corruption.
The vulnerability carries a CVSS v3.1 base score of 9.1 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H), indicating it is exploitable over the network with low complexity, no privileges or user interaction required, and unchanged scope. Remote, unauthenticated attackers can leverage it to cause unexpected system termination or corrupt kernel memory, resulting in high-impact availability disruption or integrity violations that could facilitate denial-of-service or serve as a primitive for further kernel exploitation.
Apple's security advisories, detailed in support documents such as https://support.apple.com/en-us/122066, https://support.apple.com/en-us/122068, https://support.apple.com/en-us/122069, https://support.apple.com/en-us/122070, and https://support.apple.com/en-us/122073, confirm the issue is fixed in the listed updates. Mitigation requires immediate patching to iOS 18.3/iPadOS 18.3, macOS Sequoia 15.3, macOS Sonoma 14.7.3, macOS Ventura 13.7.3, or visionOS 2.3, with no additional workarounds specified.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-3658
Vulnerability Data
An out-of-bounds write was addressed with improved input validation. This issue is fixed in iOS 18.3 and iPadOS 18.3, macOS Sequoia 15.3, macOS Sonoma 14.7.3, macOS Ventura 13.7.3, visionOS 2.3. An attacker may be able to cause unexpected system termination…
more
or corrupt kernel memory.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 7 hardening rules · 5 OS baselines
V12.1.1V12.2.1V12.3.3V17.2.2
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (including fuzzing and bounds checks) finds out-of-bounds write flaws before deployment.
Specifying and implementing required cryptography types directly precludes negotiation or acceptance of weaker algorithms.
Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.
Requiring protection of transmitted confidentiality and integrity forces selection of sufficiently strong negotiated algorithms rather than weaker ones.
Input validation can structurally reject or sanitize data that would otherwise trigger an out-of-bounds write.
Memory-protection mechanisms limit the exploitability and blast radius of a successful out-of-bounds write.
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-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.
Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.
Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.
PR.AA-04 addresses protection/verification of identity assertions in SSO/federation contexts while CWE-757 concerns protocol-level crypto algorithm negotiation, so the control neither prevents nor meaningfully mitigates the weakness.
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 and prevent out-of-bounds write defects.
Ensures network services use secure cryptographic parameters, reducing downgrade risk.
Mandates use of strong, approved cryptographic algorithms, directly preventing downgrade to weaker ones.
Secure development life cycle mandates practices that prevent out-of-bounds writes.
Application security requirements can specify bounds-checking and safe memory handling.
Secure architecture and engineering principles reduce the likelihood of buffer overflows.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Windows 10 (1 rule)
- V-220938 The LanMan authentication level must be set to send NTLMv2 response only, and to refuse LM and NTLM. prevents CWE-757
Windows 11 (1 rule)
- V-253462 The LanMan authentication level must be set to send NTLMv2 response only, and to refuse LM and NTLM. prevents CWE-757
Windows Server 2016 (1 rule)
- V-225054 The LAN Manager authentication level must be set to send NTLMv2 response only and to refuse LM and NTLM. prevents CWE-757
Windows Server 2019 (1 rule)
- V-205919 Windows Server 2019 LAN Manager authentication level must be configured to send NTLMv2 response only and to refuse LM and NTLM. prevents CWE-757
Windows Server 2022 (1 rule)
- V-254475 Windows Server 2022 LAN Manager authentication level must be configured to send NTLMv2 response only and to refuse LM and NTLM. prevents CWE-757