CVE-2025-24220
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA permissions issue was addressed with additional restrictions. This issue is fixed in iOS 18.4 and iPadOS 18.4, iPadOS 17.7.9. An app may be able to read a persistent device identifier.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA permissions issue in iOS and iPadOS allowed an application to read a persistent device identifier due to insufficient access restrictions. The vulnerability was addressed by adding additional permission checks that prevent unauthorized access to device identifiers.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 18.4< 18.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check iOS or iPadOS version on deviceOpen Settings > General > About > Version on the iPhone or iPadAffected if The version shown is less than 18.4 (for example, 18.3.x, 17.x, or earlier)
-
Confirm device model eligibility for iOS 18.4Check if the device supports iOS 18.4 by reviewing Apple's supported devices list; some older devices cannot upgrade beyond iOS 17Affected if Device hardware cannot run iOS 18.4 and is stuck on a version below 18.4
-
Check for MDM or EMM enrollment statusIf the device is managed via Mobile Device Management (Microsoft Intune, Jamf, VMware Workspace ONE, etc.), query the device inventory report for the installed OS versionAffected if Managed devices reporting iOS/iPadOS version less than 18.4 in the MDM console
A device is affected if it runs any version of iOS or iPadOS earlier than 18.4 and the persistent device identifier could have been accessed by applications prior to the permission fix.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped18.4
Deploy iOS 18.4 or iPadOS 18.4 (or iPadOS 17.7.9 for older devices) to all affected devices to apply the permission restrictions that block unauthorized access to persistent device identifiers.
iOS 18.4 or iPadOS 18.4 (or iPadOS 17.7.9 for older iPad models)
- Back up important data on the device before proceeding with the update
- Connect the device to power and ensure it is connected to Wi-Fi
- Open Settings app on the iPhone or iPad
- Navigate to General > Software Update
- Download and install iOS 18.4 (for iPhone) or iPadOS 18.4/iPadOS 17.7.9 (for iPad)
- After installation, verify the update was successful by checking Settings > General > About > Software Version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24220 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24220 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data