dbcve.org
IpadosOperating system · Apple

CVE-2023-32411

MEDIUM · 5.5 CVSS v3.1 Published 2023-06-23
Fix available
A fix is available. Upgrade to 11.7.7 / 12.6.6 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
This issue was addressed with improved entitlements. This issue is fixed in tvOS 16.5, macOS Ventura 13.4, macOS Big Sur 11.7.7, macOS Monterey 12.6.6, iOS 16.5 and iPadOS 16.5. An app may be able to bypass Privacy preferences.

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

An app could bypass Privacy preferences due to improper entitlements handling in Apple's operating systems. The vulnerability allowed applications to access privacy-protected resources without proper user authorization. This was addressed through improved entitlement validation in the patched OS versions.

MitigationUpdate to the fixed OS versions (iOS/iPadOS 16.5, macOS Ventura 13.4/macOS Monterey 12.6.6/macOS Big Sur 11.7.7, tvOS 16.5) or later. Developers should review app entitlements to ensure they request only necessary privacy permissions.

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:>= 16.0, < 16.5
Iphone OsOperating system
Affected:>= 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

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 iOS or iPadOS version on iPhone or iPad
    Go to Settings > General > About > Version, or connect device to computer and check via Apple Configurator, Finder, or Xcode
    Affected if The version shown is 16.0 through 16.4 (any build) - this indicates the device is running an affected version and may allow apps to bypass privacy preferences
  2. Check macOS version on Mac computers
    Open Terminal and run 'sw_vers -productVersion', or go to Apple menu > About This Mac
    Affected if The version is 11.0 to 11.7.6, 12.0 to 12.6.5, or 13.0 to 13.3 - these ranges indicate an affected macOS version with the entitlement validation flaw
  3. Check tvOS version on Apple TV
    Go to Settings > General > About > Version on the Apple TV device
    Affected if The version shown is any version before 16.5 - this indicates the Apple TV is running an affected tvOS version

A device is affected if it runs iOS/iPadOS 16.0-16.4, macOS 11.0-11.7.6/12.0-12.6.5/13.0-13.3, or any tvOS version below 16.5, as these contain the flawed entitlement validation that could allow apps to access privacy-protected resources without proper user authorization.

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

Update to the fixed OS versions (iOS/iPadOS 16.5, macOS Ventura 13.4/macOS Monterey 12.6.6/macOS Big Sur 11.7.7, tvOS 16.5) or later. Developers should review app entitlements to ensure they request only necessary privacy permissions.

Recommended fix High confidence

iOS 16.5 / iPadOS 16.5 / macOS Big Sur 11.7.7 / macOS Monterey 12.6.6 / macOS Ventura 13.4 / tvOS 16.5

  1. Identify the Apple device type (iPhone, iPad, Mac, or Apple TV)
  2. For iPhone/iPad: Go to Settings > General > Software Update and install iOS 16.5 / iPadOS 16.5
  3. For Mac: Go to System Settings (or System Preferences on older macOS) > General > Software Update and install the appropriate version: macOS Big Sur 11.7.7, macOS Monterey 12.6.6, or macOS Ventura 13.4
  4. For Apple TV: Go to Settings > System > Software Updates and install tvOS 16.5
  5. Verify the update was successfully installed by checking the OS version in Settings > General > About

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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