dbcve.org
IpadosOperating system · Apple

CVE-2025-24124

MEDIUM · 5.5 CVSS v3.1 Published 2025-01-27
Fix available
A fix is available. Upgrade to 2.3 / 11.3 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
The issue was addressed with improved checks. This issue is fixed in iOS 18.3 and iPadOS 18.3, iPadOS 17.7.4, macOS Sequoia 15.3, macOS Sonoma 14.7.3, macOS Ventura 13.7.3, tvOS 18.3, visionOS 2.3, watchOS 11.3. Parsing a file may lead to an unexpected app termination.

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 · moderate confidence

This is an Apple operating system vulnerability affecting iOS, iPadOS, macOS, tvOS, visionOS, and watchOS. The issue involves parsing files that can trigger an unexpected app termination (crash), likely due to insufficient input validation or bounds checking during file processing. Apple addressed this with improved validation checks in the specified version updates.

MitigationUpdate all affected Apple devices to the fixed versions (iOS 18.3/iPadOS 18.3/17.7.4, macOS Sequoia 15.3/Sonoma 14.7.3/Ventura 13.7.3, tvOS 18.3, visionOS 2.3, watchOS 11.3) to remediate this vulnerability.

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
IpadosOperating system
Affected:< 17.7.4>= 18.0, < 18.3
Iphone OsOperating system
Affected:< 18.3
macOSOperating system
Affected:< 13.7.3>= 14.0, < 14.7.3>= 15.0, < 15.3
TvosOperating system
Affected:< 18.3
VisionosOperating system
Affected:< 2.3
WatchosOperating system
Affected:< 11.3

CVSS 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify your iOS or iPadOS version
    On iPhone: Settings > General > About > Version. On iPad: Settings > General > About > Version. Note the version number (e.g., 18.2, 17.7.3).
    Affected if Version is less than 17.7.4, or 18.0 to less than 18.3 (iPadOS). For iPhone (iOS), version is less than 18.3.
  2. Identify your macOS version
    Open System Settings > About, or run the command 'sw_vers' in Terminal. Note the version number (e.g., 15.2, 14.6).
    Affected if Version is less than 13.7.3, or 14.0 to less than 14.7.3, or 15.0 to less than 15.3.
  3. Identify your tvOS version
    Go to Settings > General > About > Version. Note the version number.
    Affected if Version is less than 18.3.
  4. Identify your watchOS version
    On Apple Watch: Settings > General > About. Or on iPhone, open the Watch app > My Watch > General > About. Note the version number.
    Affected if Version is less than 11.3.
  5. Identify your visionOS version
    Go to Settings > General > About > Version. Note the version number.
    Affected if Version is less than 2.3.

You are affected if your device runs any version of iOS, iPadOS, macOS, tvOS, watchOS, or visionOS that falls within the vulnerable version ranges listed for this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.3 / 11.3 / 13.7.3 or later
Fixed in 2.311.313.7.3
Interim mitigation

Update all affected Apple devices to the fixed versions (iOS 18.3/iPadOS 18.3/17.7.4, macOS Sequoia 15.3/Sonoma 14.7.3/Ventura 13.7.3, tvOS 18.3, visionOS 2.3, watchOS 11.3) to remediate this vulnerability.

Recommended fix High confidence

iOS 18.3, iPadOS 18.3, iPadOS 17.7.4, macOS Ventura 13.7.3, macOS Sonoma 14.7.3, macOS Sequoia 15.3, tvOS 18.3, visionOS 2.3, watchOS 11.3

  1. For iOS and iPadOS: Go to Settings > General > Software Update and install iOS 18.3/iPadOS 18.3, or for older devices iPadOS 17.7.4
  2. For macOS: Open System Settings > General > Software Update and install the appropriate version (Ventura 13.7.3, Sonoma 14.7.3, or Sequoia 15.3)
  3. For tvOS: Go to Settings > General > Software Update > Update Software and install tvOS 18.3
  4. For visionOS: Go to Settings > General > Software Update and install visionOS 2.3
  5. For watchOS: On the paired iPhone, open the Watch app, go to General > Software Update and install watchOS 11.3

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24124 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24124 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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