CVE-2025-24201: Apple Multiple Products WebKit Out-of-Bounds Write Vulnerability

What it is

An out-of-bounds write issue was addressed with improved checks to prevent unauthorized actions. This issue is fixed in Safari 18.3.1, iOS 15.8.4 and iPadOS 15.8.4, iOS 16.7.11 and iPadOS 16.7.11, iOS 18.3.2 and iPadOS 18.3.2, iPadOS 17.7.6, macOS Sequoia 15.3.2, visionOS 2.3.2, watchOS 11.4. Maliciously crafted web content may be able to break out of Web Content sandbox. This is a supplementary fix for an attack that was blocked in iOS 17.2. (Apple is aware of a report that this issue may have been exploited in an extremely sophisticated attack against specific targeted individuals on versions of iOS before iOS 17.2.).

Exploitation evidence

First exploit evidence seen: 2025-03-13 (earliest date across the sources below).

Exploited in the wild

• CISA KEV: listed since 2025-03-13. Source

Public exploit code

GitHub proof-of-concept repositories below quality bar

2 public repositories from 2 accounts, first seen 2025-07-11.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: CISA KEV · nomi-sec/PoC-in-GitHub.

How to fix it

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. (source: CISA KEV)

Fixed versions

• apple safari: upgrade to 18.3.1 or later
• apple macos: upgrade to 15.3.2 or later (affected from 15.0)
• apple visionos: upgrade to 2.3.2 or later
• apple watchos: upgrade to 11.4 or later
• apple ipados: upgrade to 15.8.4 or later (affected from 15.8)
• apple ipados: upgrade to 16.7.11 or later (affected from 16.7)
• apple ipados: upgrade to 17.7.6 or later (affected from 17.0)
• apple ipados: upgrade to 18.3.2 or later (affected from 18.0)
• apple iphone os: upgrade to 15.8.4 or later (affected from 15.8)
• apple iphone os: upgrade to 16.7.11 or later (affected from 16.7)
• apple iphone os: upgrade to 18.3.2 or later (affected from 17.0)

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

• https://support.apple.com/en-us/122281 (CISA KEV notes)
• https://support.apple.com/en-us/122283 (CISA KEV notes)
• https://support.apple.com/en-us/122284 (CISA KEV notes)
• https://support.apple.com/en-us/122285 (CISA KEV notes)
• https://support.apple.com/en-us/122345 (Release Notes, Vendor Advisory)
• https://support.apple.com/en-us/122346 (Release Notes, Vendor Advisory)
• https://support.apple.com/en-us/122372 (Release Notes, Vendor Advisory)
• https://support.apple.com/en-us/122376 (Release Notes, Vendor Advisory)

MITRE ATT&CK mitigations for this chain

• M1050 Exploit Protection (for T1189) : Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior. Control flow integrity checking is another way to potentially identify and stop a software exploit
• M1051 Update Software (for T1189) : Ensuring that all browsers and plugins are kept updated can help prevent the exploit phase of this technique. Use modern browsers with security features turned on.
• M1048 Application Isolation and Sandboxing (for T1189) : Browser sandboxes can be used to mitigate some of the impact of exploitation, but sandbox escapes may still exist. Other types of virtualization and application microsegmentation may also mitigate the impact of client-side exploitation. The risks of additional exploits and weaknesses in implementation may still exist
• M1021 Restrict Web-Based Content (for T1189, T1059) : Adblockers can help prevent malicious code served through ads from executing in the first place. Script blocking extensions can also help to prevent the execution of JavaScript. Consider disabling browser push notifications from certain applications and browsers.
• M1017 User Training (for T1189) : Train users to be aware of access or manipulation attempts by an adversary to reduce the risk of successful spearphishing, social engineering, and other techniques that involve user interaction.
• M1033 Limit Software Installation (for T1059) : Prevent user installation of unrequired command and scripting interpreters.
• M1045 Code Signing (for T1059) : Where possible, only permit execution of signed scripts.
• M1042 Disable or Remove Feature or Program (for T1059) : Disable or remove any unnecessary or unused shells or interpreters.
• M1038 Execution Prevention (for T1059) : Use application control where appropriate. For example, PowerShell Constrained Language mode can be used to restrict access to sensitive or otherwise dangerous language elements such as those used to execute arbitrary Windows APIs or files (e.g., `Add-Type`).
• M1049 Antivirus/Antimalware (for T1059) : Anti-virus can be used to automatically quarantine suspicious files.

Detection Generic guidance

• Initial Access: Alert on unusual requests to the affected service (odd paths, oversized payloads, exploit strings) in WAF, reverse-proxy and application logs.
• Execution: Watch for the service process spawning shells or script interpreters (cmd.exe, powershell, sh, bash, python) via EDR process-tree rules.

Response checklist Generic guidance

1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.