dbcve.org
IpadosOperating system · Apple

CVE-2025-24179

MEDIUM · 5.7 CVSS v3.1 Published 2025-04-29
Fix available
A fix is available. Upgrade to 2.3 / 13.7.5 or later.
See remediation →
60/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
A null pointer dereference was addressed with improved input validation. This issue is fixed in iOS 18.3 and iPadOS 18.3, iPadOS 17.7.6, macOS Sequoia 15.3, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.3, visionOS 2.3. An attacker on the local network may be able to cause a denial-of-service.

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 confidence

A null pointer dereference vulnerability in Apple operating systems allows an attacker on the local network to cause a denial-of-service by sending specially crafted malformed input that lacks proper validation, triggering a crash.

MitigationApply the available security updates: iOS 18.3, iPadOS 18.3/17.7.6, macOS Sequoia 15.3/Sonoma 14.7.5/Ventura 13.7.5, tvOS 18.3, and visionOS 2.3.

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.6>= 18.0, < 18.3
Iphone OsOperating system
Affected:< 18.3
macOSOperating system
Affected:< 13.7.5>= 14.0, < 14.7.5>= 15.0, < 15.3
TvosOperating system
Affected:< 18.3
VisionosOperating system
Affected:< 2.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
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/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 Apple operating system product
    Check the device type: iPhone, iPad, Mac, Apple TV, or Apple Vision Pro. This determines which version range applies.
    Affected if The device runs any of the affected Apple OS types (iOS, iPadOS, macOS, tvOS, visionOS)
  2. Check iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About and note the Version number.
    Affected if Version is less than 18.3, or is 17.x and less than 17.7.6, or is 18.0-18.2.x
  3. Check macOS version
    On Mac, go to System Settings > About (or Apple menu > About This Mac) and note the version number listed.
    Affected if Version is less than 13.7.5, or is 14.0-14.7.4, or is 15.0-15.2.x
  4. Check tvOS version
    On Apple TV, go to Settings > General > About and note the Version number.
    Affected if Version is less than 18.3
  5. Check visionOS version
    On Apple Vision Pro, go to Settings > About and note the Version number.
    Affected if Version is less than 2.3

You are affected if your device runs any of the Apple operating systems listed and its version falls within the vulnerable ranges specified for your product.

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 / 13.7.5 / 14.7.5 or later
Fixed in 2.313.7.514.7.5
Interim mitigation

Apply the available security updates: iOS 18.3, iPadOS 18.3/17.7.6, macOS Sequoia 15.3/Sonoma 14.7.5/Ventura 13.7.5, tvOS 18.3, and visionOS 2.3.

Recommended fix High confidence

iOS 18.3/iPadOS 18.3 or iPadOS 17.7.6 (depending on device); macOS Ventura 13.7.5/Sonoma 14.7.5/Sequoia 15.3; tvOS 18.3; visionOS 2.3

  1. Check current iOS/iPadOS version: Settings > General > About > Version
  2. Check current macOS version: Apple menu > About This Mac
  3. Check current tvOS version: Settings > General > About > Version
  4. Check current visionOS version: Settings > General > About > Version
  5. For iPhone/iPad: Go to Settings > General > Software Update and install the available update
  6. For Mac: Go to System Settings > General > Software Update and install the available update
  7. For Apple TV: Go to Settings > General > Software Update and install the available update
  8. For Vision Pro: Go to Settings > General > Software Update and install the available update

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA1.0 h
12.0 hours of engineering $2,110
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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