Cyber Resilience

CVE-2025-24213

Memory Safety in Apple Ipados ≤ 17.7.6

Memory Safety
Published
31 March 2025
Modified
02 April 2026
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0040 33th percentile
Risk Priority 57 floored blend · peak EPSS

Summary

CVE-2025-24213 is a high-severity Type Confusion (CWE-843) vulnerability in Apple Ipados. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 33th percentile by exploit likelihood (below the median); 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-8 (Security and Privacy Engineering Principles) — 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-24213 is a type confusion vulnerability (CWE-843) stemming from improper handling of floats, which could lead to memory corruption. The issue affects multiple Apple platforms and components, including Safari prior to version 18.5, iOS prior to 18.5, iPadOS prior to 18.5 and 17.7.7, macOS Sequoia prior to 15.5, tvOS prior to 18.5, visionOS prior to 2.5, and watchOS prior to 11.5.

The vulnerability has a CVSS v3.1 base score of 7.8 (High), with local attack vector (AV:L), low attack complexity (AC:L), no privileges required (PR:N), and required user interaction (UI:R). A local attacker could exploit it to achieve high impacts on confidentiality, integrity, and availability (C:H/I:H/A:H), potentially enabling arbitrary code execution through memory corruption upon successful type confusion.

Apple addressed the issue through improved float handling in the listed fixed versions. Official advisories detailing the patches are available at https://support.apple.com/en-us/122404, https://support.apple.com/en-us/122405, https://support.apple.com/en-us/122716, https://support.apple.com/en-us/122719, and https://support.apple.com/en-us/122720. Security practitioners should prioritize updating affected devices to mitigate exposure.

EU & UK References

Vulnerability Data

This issue was addressed with improved handling of floats. This issue is fixed in Safari 18.5, iOS 18.5 and iPadOS 18.5, iPadOS 17.7.7, macOS Sequoia 15.5, tvOS 18.5, visionOS 2.5, watchOS 11.5. A type confusion issue could lead to memory…

more

corruption.

CWE(s)
CWE-843

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2022-42856Same product: Apple Ipados
CVE-2024-23222Same product: Apple Ipados
CVE-2023-23529Same product: Apple Ipados
CVE-2026-43705Same product: Apple Ipados
CVE-2024-54505Same product: Apple Ipados
CVE-2025-31206Same product: Apple Ipados
CVE-2025-30445Same product: Apple Ipados
CVE-2025-43541Same product: Apple Ipados
CVE-2023-27930Same product: Apple Ipados
CVE-2023-32358Same product: Apple Ipados

Affected Assets

apple
safari
≤ 18.4
apple
ipados
≤ 17.7.6 · 18.0 — 18.4
apple
iphone os
≤ 18.4
apple
macos
15.0 — 15.4
apple
tvos
≤ 18.4

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.5.2
  • V3.2.3
  • V15.3.5

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (including fuzzing and type-aware analysis) directly finds type-confusion flaws before deployment.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can require use of type-safe languages, static typing, and runtime type checks that structurally avoid allocating one type and accessing another.

SI-16 Memory Protection partial match

Memory-protection controls limit the blast radius when a type-confusion access occurs but do not stop the flaw itself.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent type-confusion flaws via safe typing, static analysis, and code review while the control itself addresses many additional 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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect type-confusion vulnerabilities through fuzzing and static analysis.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates type-safe design and review that can catch type-confusion flaws.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify strong typing and interface contracts that reduce type confusion.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles promote type-safe languages and memory-safety mechanisms that mitigate type confusion.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly forbid unsafe type casts and require static-analysis checks for type confusion.

References