dbcve.org
IpadosOperating system · Apple

CVE-2025-24214

MEDIUM · 5.5 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 2.4 / 15.4 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 privacy issue was addressed by not logging contents of text fields. This issue is fixed in iOS 18.4 and iPadOS 18.4, macOS Sequoia 15.4, tvOS 18.4, visionOS 2.4, watchOS 11.4. An app may be able to access sensitive user data.

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 privacy vulnerability where text field contents were being logged (written to system logs) which could be accessed by an application, potentially exposing sensitive user data such as passwords, personal information, or credentials entered into text fields.

MitigationApply the vendor-supplied OS updates: iOS 18.4, iPadOS 18.4, macOS Sequoia 15.4, tvOS 18.4, visionOS 2.4, or watchOS 11.4. For enterprise environments, deploy these updates via mobile device management (MDM) or software update mechanisms.

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:>= 15.0, < 15.4
TvosOperating system
Affected:< 18.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. Identify your Apple device type
    Determine whether the device is an iPhone, iPad, Mac, Apple TV, or Vision Pro. This is needed because different product lines have different version schemes and vulnerability thresholds.
    Affected if The device runs any of the affected product lines (iPadOS, iPhone OS, macOS, tvOS, or visionOS)
  2. Check the installed iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About to view the software version. Alternatively, run 'sw_vers' in Terminal or use the MDM console to query the device OS version.
    Affected if The version is below 18.4 (for example, 18.3.x, 18.2.x, or earlier)
  3. Check the installed macOS version
    On Mac, go to System Settings > About or run 'sw_vers' in Terminal to see the macOS version number.
    Affected if The version is 15.0, 15.1, 15.2, or 15.3 (any version from 15.0 up to but not including 15.4)
  4. Check the installed tvOS or visionOS version
    On Apple TV, go to Settings > General > About > Version. On Vision Pro, go to Settings > General > About. Alternatively, query through MDM or the device management console.
    Affected if The tvOS version is below 18.4, or the visionOS version is below 2.4

The environment is affected if any managed Apple device runs iOS/iPadOS below 18.4, macOS 15.0-15.3, tvOS below 18.4, or visionOS below 2.4, as text field inputs may have been logged to system logs in these versions.

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 / 15.4 / 18.4 or later
Fixed in 2.415.418.4
Interim mitigation

Apply the vendor-supplied OS updates: iOS 18.4, iPadOS 18.4, macOS Sequoia 15.4, tvOS 18.4, visionOS 2.4, or watchOS 11.4. For enterprise environments, deploy these updates via mobile device management (MDM) or software update mechanisms.

Recommended fix High confidence

iOS 18.4 / iPadOS 18.4 / macOS Sequoia 15.4 / tvOS 18.4 / visionOS 2.4 (depending on device)

  1. For iPhone: Go to Settings > General > Software Update and install iOS 18.4 or later
  2. For iPad: Go to Settings > General > Software Update and install iPadOS 18.4 or later
  3. For Mac: Go to System Settings > General > Software Update and install macOS Sequoia 15.4 or later
  4. For Apple TV: Go to Settings > General > System > Software Update and install tvOS 18.4 or later
  5. For Vision Pro: Go to Settings > General > Software Update and install visionOS 2.4 or later
  6. After updating, verify the update was successful by checking the OS version in Settings
Caveat Standard OS update considerations apply - ensure app compatibility and back up data before updating

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

Fix this in Ipados Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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