dbcve.org
IpadosOperating system · Apple

CVE-2025-30432

MEDIUM · 6.4 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 2.4 / 13.7.5 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 logic issue was addressed with improved state management. This issue is fixed in iOS 18.4 and iPadOS 18.4, iPadOS 17.7.6, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.4, visionOS 2.4, watchOS 11.4. A malicious app may be able to attempt passcode entries on a locked device and thereby cause escalating time delays after 4 failures.

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 malicious app can exploit a logic flaw in state management to attempt passcode entries on a locked iOS/macOS device without triggering the normal escalating time delays that should occur after 4 failed attempts. This bypass of the lockout mechanism could facilitate brute-force passcode attacks.

MitigationApply the vendor-supplied patches: update to iOS 18.4, iPadOS 18.4 or 17.7.6, macOS Sonoma 14.7.5 or Ventura 13.7.5, tvOS 18.4, visionOS 2.4, or watchOS 11.4 as appropriate for the affected device.

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.4
Iphone OsOperating system
Affected:< 18.4
macOSOperating system
Affected:>= 13.0, < 13.7.5>= 14.0, < 14.7.5
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
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
Low

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

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 and operating system
    Determine whether the device is an iPhone, iPad, Mac, Apple TV, or Vision Pro and note the installed OS version (Settings > General > About on iOS/iPadOS, System Settings > About This Mac on macOS, Settings > General > About on tvOS, Settings > General > About on visionOS)
    Affected if The device runs any of the affected Apple operating systems and the version falls outside the fixed releases (iOS 18.4 or 17.7.6, iPadOS 18.4 or 17.7.6, macOS 13.7.5 or 14.7.5, tvOS 18.4, visionOS 2.4)
  2. Verify iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About and check the Version number. Compare against < 17.7.6, or >= 18.0 and < 18.4
    Affected if iOS or iPadOS version is earlier than 17.7.6, or is 18.0 through 18.3.x
  3. Verify macOS version
    On Mac, go to System Settings > General > About This Mac or use 'sw_vers' command in Terminal. Compare against >= 13.0, < 13.7.5 or >= 14.0, < 14.7.5
    Affected if macOS version is 13.0 through 13.7.4, or 14.0 through 14.7.4
  4. Verify tvOS version
    On Apple TV, go to Settings > General > About > Version. Compare against < 18.4
    Affected if tvOS version is earlier than 18.4
  5. Verify visionOS version
    On Apple Vision Pro, go to Settings > General > About. Compare against < 2.4
    Affected if visionOS version is earlier than 2.4

If the device runs any iOS, iPadOS, macOS, tvOS, or visionOS version within the affected ranges listed, the environment is vulnerable to the passcode lockout bypass.

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 vendor-supplied patches: update to iOS 18.4, iPadOS 18.4 or 17.7.6, macOS Sonoma 14.7.5 or Ventura 13.7.5, tvOS 18.4, visionOS 2.4, or watchOS 11.4 as appropriate for the affected device.

Recommended fix High confidence

iOS 18.4 / iPadOS 18.4 / iPadOS 17.7.6 / macOS 14.7.5 / macOS 13.7.5 / tvOS 18.4 / visionOS 2.4 / watchOS 11.4

  1. For iPhone: Go to Settings > General > Software Update and install iOS 18.4
  2. For iPad: Go to Settings > General > Software Update and install iPadOS 18.4 (or iPadOS 17.7.6 if unable to upgrade to 18.x)
  3. For Mac: Go to System Settings > General > Software Update and install macOS 14.7.5 (Sonoma) or macOS 13.7.5 (Ventura)
  4. For Apple TV: Go to Settings > System > Software Updates and install tvOS 18.4
  5. For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 2.4
  6. For Apple Watch: Go to the Watch app on iPhone > General > Software Update and install watchOS 11.4

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
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,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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