dbcve.org
IpadosOperating system · Apple

CVE-2023-32413

HIGH · 7.0 CVSS v3.1 Published 2023-06-23
Fix available
A fix is available. Upgrade to 9.5 / 11.7.7 or later.
See remediation →
73/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 race condition was addressed with improved state handling. This issue is fixed in watchOS 9.5, tvOS 16.5, macOS Ventura 13.4, iOS 15.7.6 and iPadOS 15.7.6, macOS Big Sur 11.7.7, macOS Monterey 12.6.6, iOS 16.5 and iPadOS 16.5. An app may be able to gain root privileges.

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

A race condition in Apple operating systems allows a malicious application to gain root privileges through improper state handling during execution. The vulnerability enables local privilege escalation by exploiting timing-dependent operations.

MitigationApply the vendor-supplied security updates for the affected Apple products: iOS 15.7.6/16.5, iPadOS 15.7.6/16.5, macOS Ventura 13.4, macOS Big Sur 11.7.7, macOS Monterey 12.6.6, watchOS 9.5, and tvOS 16.5.

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:< 15.7.6>= 16.0, < 16.5
Iphone OsOperating system
Affected:< 15.7.6>= 16.0, < 16.5
macOSOperating system
Affected:>= 11.0, < 11.7.7>= 12.0, < 12.6.6>= 13.0, < 13.4
TvosOperating system
Affected:< 16.5
WatchosOperating system
Affected:< 9.5

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

CVSS:3.1/AV:L/AC:H/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 the device operating system
    On the device, go to Settings > General > About (iOS/iPadOS) or System Settings > About (macOS) to view the exact OS name and version number
    Affected if The device runs any of the affected Apple operating systems (iOS, iPadOS, macOS, tvOS, watchOS)
  2. Check iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About and note the Version field (for example, 16.4 or 15.7.5)
    Affected if Version is less than 15.7.6, or between 16.0 and 16.4 inclusive
  3. Check macOS version
    Open Terminal and run 'sw_vers -productVersion' or go to System Settings > About to see the macOS version (for example, 13.3 or 12.6.5)
    Affected if Version is 11.0 to 11.7.6, 12.0 to 12.6.5, or 13.0 to 13.3 inclusive
  4. Check tvOS or watchOS version
    On Apple TV, go to Settings > General > About. On Apple Watch, open the Watch app on iPhone and go to General > About
    Affected if tvOS version is below 16.5, or watchOS version is below 9.5

If the installed OS version falls within any of the affected ranges for iOS (< 15.7.6 or >= 16.0, < 16.5), iPadOS (< 15.7.6 or >= 16.0, < 16.5), macOS (11.0-11.7.6, 12.0-12.6.5, or 13.0-13.3), tvOS (< 16.5), or watchOS (< 9.5), the device is potentially affected by this privilege escalation vulnerability.

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 9.5 / 11.7.7 / 12.6.6 or later
Fixed in 9.511.7.712.6.6
Interim mitigation

Apply the vendor-supplied security updates for the affected Apple products: iOS 15.7.6/16.5, iPadOS 15.7.6/16.5, macOS Ventura 13.4, macOS Big Sur 11.7.7, macOS Monterey 12.6.6, watchOS 9.5, and tvOS 16.5.

Recommended fix High confidence

iOS/iPadOS 15.7.6 or 16.5; macOS 11.7.7/12.6.6/13.4; tvOS 16.5; watchOS 9.5 (depending on device)

  1. Identify the Apple device type (iPhone, iPad, Mac, Apple Watch, or Apple TV)
  2. Check the current OS version in Settings > General > About (iOS/iPadOS) or System Preferences > About (macOS)
  3. Back up the device before updating
  4. For iPhone/iPad: Go to Settings > General > Software Update and upgrade to iOS/iPadOS 15.7.6 or iOS/iPadOS 16.5
  5. For Mac: Go to System Preferences > Software Update and upgrade to macOS 11.7.7 (Big Sur), 12.6.6 (Monterey), or 13.4 (Ventura)
  6. For Apple TV: Go to Settings > System > Software Updates and upgrade to tvOS 16.5
  7. For Apple Watch: Go to Settings > General > Software Update on the Watch app on iPhone and upgrade to watchOS 9.5

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,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 $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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