dbcve.org
IpadosOperating system · Apple

CVE-2025-24137

HIGH · 8.0 CVSS v3.1 Published 2025-01-27
Fix available
A fix is available. Upgrade to 2.3 / 11.3 or later.
See remediation →
83/100
Remediation priority · High
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
A type confusion 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, tvOS 18.3, visionOS 2.3. An attacker on the local network may corrupt process memory.

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 a type confusion vulnerability in Apple operating systems (iOS, iPadOS, macOS, tvOS, visionOS) where an attacker on the local network can corrupt process memory. Type confusion occurs when code improperly handles object type checking, leading to memory corruption that could potentially be exploited for code execution or denial of service.

MitigationApply the security updates: iOS 18.3, iPadOS 18.3, iPadOS 17.7.4, macOS Sequoia 15.3, macOS Sonoma 14.7.3, tvOS 18.3, or visionOS 2.3. For network-exposed systems, restrict local network access as an interim control.

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:< 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
Adjacent
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 device model and OS platform
    Determine whether the device is an iPhone, iPad, Mac, Apple TV, Vision Pro, or Apple Watch. For Macs, run `sw_vers` in Terminal. For iOS/iPadOS, check Settings > General > About. For tvOS, go to Settings > General > About. For visionOS, check Settings > General > About. For watchOS, use the Watch app on paired iPhone or Settings > General > About on the watch.
    Affected if The device runs any of the affected Apple operating systems listed in the CVE.
  2. Check installed iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > Software Update to view the current version, or check Settings > General > About for the version number. Compare against the affected ranges: iOS < 18.3, iPadOS < 17.7.4 or >= 18.0 and < 18.3.
    Affected if The installed iOS version is below 18.3, or iPadOS is below 17.7.4 or between 18.0 and 18.3.
  3. Check installed macOS version
    Open System Settings > About, or run `sw_vers` in Terminal to display the macOS version. Compare against the affected ranges: macOS < 14.7.3 or >= 15.0 and < 15.3.
    Affected if The installed macOS version is below 14.7.3 or between 15.0 and 15.3.
  4. Check installed tvOS or visionOS version
    On Apple TV, go to Settings > General > About to see the tvOS version. On Vision Pro, go to Settings > General > About. Compare tvOS against < 18.3 and visionOS against < 2.3.
    Affected if The installed tvOS is below 18.3 or visionOS is below 2.3.
  5. Check installed watchOS version
    On Apple Watch, go to Settings > General > About, or open the Watch app on paired iPhone and navigate to General > About. Compare against affected range: watchOS < 11.3.
    Affected if The installed watchOS is below 11.3.
  6. Assess local network exposure
    Review network configuration to determine if the device is exposed to untrusted local network devices. For macOS, check System Settings > Network. For iOS/iPadOS, review connected Wi-Fi networks and VPN configurations.
    Affected if The device is on a network with untrusted or potentially malicious local attackers, as the CVE notes exploitation occurs from the local network.

The device is affected if it runs any Apple operating system version below the fixed releases (iOS 18.3, iPadOS 17.7.4/18.3, macOS 14.7.3/15.3, tvOS 18.3, visionOS 2.3, watchOS 11.3) and is accessible to local network attackers.

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 / 14.7.3 or later
Fixed in 2.311.314.7.3
Interim mitigation

Apply the security updates: iOS 18.3, iPadOS 18.3, iPadOS 17.7.4, macOS Sequoia 15.3, macOS Sonoma 14.7.3, tvOS 18.3, or visionOS 2.3. For network-exposed systems, restrict local network access as an interim control.

Recommended fix High confidence

iOS 18.3 / iPadOS 17.7.4 or 18.3 / macOS 14.7.3 or 15.3 / tvOS 18.3 / visionOS 2.3 / watchOS 11.3

  1. Identify the Apple device type (iPhone, iPad, Mac, Apple TV, Apple Vision Pro, Apple Watch)
  2. For iPhone: Upgrade to iOS 18.3 or later
  3. For iPad: Upgrade to iPadOS 17.7.4 or iPadOS 18.3 (depending on which iPadOS version branch is in use)
  4. For Mac: Upgrade to macOS Sonoma 14.7.3 or macOS Sequoia 15.3 (depending on which macOS version is installed)
  5. For Apple TV: Upgrade to tvOS 18.3
  6. For Apple Vision Pro: Upgrade to visionOS 2.3
  7. For Apple Watch: Upgrade to watchOS 11.3
  8. On the device, go to Settings > General > Software Update to download and install the update
Caveat Standard Apple OS updates may include minor UI changes; ensure backups exist before updating

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

Fix this in Ipados Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24137 — 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-24137 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