dbcve.org
IpadosOperating system · Apple

CVE-2025-30470

MEDIUM · 5.5 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 2.4 / 13.7.5 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
A path handling issue was addressed with improved logic. This issue is fixed in iOS 18.4 and iPadOS 18.4, macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, visionOS 2.4, watchOS 11.4. An app may be able to read sensitive location information.

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 path handling vulnerability in Apple operating systems allowed a malicious or compromised application to access sensitive location information through improper path validation. The issue stemmed from insufficient path sanitization that could be exploited to traverse to protected location data files outside the app's intended sandbox boundaries.

MitigationApply the relevant OS updates (iOS 18.4, iPadOS 18.4, macOS Sequoia 15.4/Sonoma 14.7.5/Ventura 13.7.5, visionOS 2.4, or watchOS 11.4) to address the path handling logic flaw.

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:< 18.4
Iphone OsOperating system
Affected:< 18.4
macOSOperating system
Affected:< 13.7.5>= 14.0, < 14.7.5>= 15.0, < 15.4
VisionosOperating system
Affected:< 2.4

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
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 checks

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

  1. Check installed iOS or iPadOS version
    Go to Settings > General > About and note the Version number (e.g., 18.3.1)
    Affected if The version is less than 18.4 (e.g., 18.3, 17.x, etc.) and Location Services are enabled in Settings > Privacy & Security > Location Services
  2. Check installed macOS version
    Go to System Settings > About and note the Version number (e.g., 14.3.1)
    Affected if The version falls within any of these affected ranges: < 13.7.5, >= 14.0 and < 14.7.5, or >= 15.0 and < 15.4, and Location Services are enabled in System Settings > Privacy & Security > Location Services
  3. Check installed visionOS version
    Go to Settings > About and note the Version number (e.g., 2.3.1)
    Affected if The version is less than 2.4 and Location Services are enabled in Settings > Privacy > Location Services
  4. Verify Location Services status
    Check if Location Services are enabled: iOS/iPadOS: Settings > Privacy & Security > Location Services (toggle should be visible); macOS: System Settings > Privacy & Security > Location Services; visionOS: Settings > Privacy > Location Services
    Affected if Location Services are currently enabled on the device

You are likely affected if your OS version is below the patched release (iOS/iPadOS 18.4, macOS 15.4/14.7.5/13.7.5, visionOS 2.4) AND Location Services are enabled, as the path traversal could allow a malicious app to access location data files outside its sandbox.

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

Apply the relevant OS updates (iOS 18.4, iPadOS 18.4, macOS Sequoia 15.4/Sonoma 14.7.5/Ventura 13.7.5, visionOS 2.4, or watchOS 11.4) to address the path handling logic flaw.

Recommended fix High confidence

iOS/iPadOS 18.4, macOS Ventura 13.7.5, macOS Sonoma 14.7.5, macOS Sequoia 15.4, visionOS 2.4

  1. For iPhone: Upgrade to iOS 18.4 via Settings > General > Software Update
  2. For iPad: Upgrade to iPadOS 18.4 via Settings > General > Software Update
  3. For Mac (Ventura): Upgrade to macOS 13.7.5 via System Settings > General > Software Update
  4. For Mac (Sonoma): Upgrade to macOS 14.7.5 via System Settings > General > Software Update
  5. For Mac (Sequoia): Upgrade to macOS 15.4 via System Settings > General > Software Update
  6. For Vision Pro: Upgrade to visionOS 2.4 via Settings > General > Software Update
Caveat Standard OS update considerations apply - review Apple release notes for any behavior changes before deploying in production environments

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

Fix this in Ipados Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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