CVERadar
MEDIUM · CVSS 3.1 5Public PoCEPSS 0.64% (p50)Threat level 29

CVE-2025-24203: CVE-2025-24203: The issue was addressed with improved checks. This issue is fixed in iOS 18.4 and iPadOS 1…

apple · ipad os · NVD published 2025-04-01 · posted 2025-05-09 · last modified 2026-06-17

What it is

The issue was addressed with improved checks. This issue is fixed in iOS 18.4 and iPadOS 18.4, iPadOS 17.7.6, macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.4, visionOS 2.4, watchOS 11.4. An app may be able to modify protected parts of the file system.

WeaknessNot specified
CVSS vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N (source: 134c704f-9b21-4f2e-91b3-4a467353bcc0)
ATT&CK tacticsn/a

Exploitation evidence

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

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

GitHub proof-of-concept repositories

3 public repositories from 3 accounts, first seen 2025-05-09. Most starred: jailbreakdotparty/dirtyZero (428 stars), view repository.

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: nomi-sec/PoC-in-GitHub.

How to fix it

Fixed versions

  • apple ipad os: upgrade to 17.7.6 or later
  • apple macos: upgrade to 13.7.5 or later (affected from 13.0)
  • apple macos: upgrade to 14.7.5 or later (affected from 14.0)
  • apple macos: upgrade to 15.4 or later (affected from 15.0)

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

Vendor advisories and patches

Detection Generic guidance

    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.

    Sources