dbcve.org
IpadosOperating system · Apple

CVE-2023-32407

MEDIUM · 5.5 CVSS v3.1 Published 2023-06-23
Fix available
A fix is available. Upgrade to 9.5 / 11.7.7 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 logic issue was addressed with improved state management. 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 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

A logic flaw in Apple's state management allows a malicious application to bypass Privacy preferences, potentially accessing protected resources such as Contacts, Photos, Location, or other privacy-sensitive data without proper user authorization.

MitigationApply the relevant Apple security updates (watchOS 9.5, tvOS 16.5, macOS Ventura 13.4/Big Sur 11.7.7/Monterey 12.6.6, iOS 15.7.6/16.5, iPadOS 15.7.6/16.5) to all affected devices to remediate this vulnerability.

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= 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
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. Identify your Apple device type and OS
    On iOS/iPadOS go to Settings > General > About; on macOS go to System Settings > General > About or System Preferences > General; on tvOS go to Settings > General > About; on watchOS go to Settings > General > About
    Affected if You cannot determine the exact OS version or the version falls into the affected ranges below
  2. Check iOS or iPadOS version
    View the Version number in the About section. Affected versions are: < 15.7.6, or >= 16.0 and < 16.5
    Affected if Your iOS or iPadOS version is 15.7.5 or earlier, or any version from 16.0 through 16.4.x
  3. Check macOS version
    View the Version number in the About section. Affected versions are: >= 11.0 and < 11.7.7; >= 12.0 and < 12.6.6; >= 13.0 and < 13.4
    Affected if Your macOS version is Big Sur 11.0-11.7.6, Monterey 12.0-12.6.5, or Ventura 13.0-13.3.x
  4. Check tvOS version
    View the Version number in the About section. Affected versions are: any version < 16.5
    Affected if Your tvOS version is 16.4.x or earlier
  5. Check watchOS version
    View the Version number in the About section. Affected versions are: < 9.5 or = 9.5
    Affected if Your watchOS version is 9.5 or any earlier version

You are affected if your device runs any iOS/iPadOS version listed, any macOS version listed, any tvOS version before 16.5, or watchOS 9.5 or earlier.

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 relevant Apple security updates (watchOS 9.5, tvOS 16.5, macOS Ventura 13.4/Big Sur 11.7.7/Monterey 12.6.6, iOS 15.7.6/16.5, iPadOS 15.7.6/16.5) to all affected devices to remediate this vulnerability.

Recommended fix High confidence

iOS 15.7.6/iOS 16.5, iPadOS 15.7.6/iPadOS 16.5, macOS 11.7.7/12.6.6/13.4, tvOS 16.5, watchOS 9.5 (or later)

  1. Back up your device using iCloud or your computer before updating
  2. For iOS/iPadOS: Open Settings > General > Software Update and download/install iOS 15.7.6 or iOS 16.5 (depending on your device compatibility)
  3. For macOS: Open System Preferences (System Settings on Ventura) > Software Update and install the recommended security update (macOS 11.7.7, 12.6.6, or 13.4)
  4. For tvOS: Go to Settings > System > Software Updates and install tvOS 16.5
  5. For watchOS: Open the Watch app on iPhone, go to My Watch > General > Software Update and install watchOS 9.5 (or a later version if available)
  6. After updating, verify the new version is installed 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
  • 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-32407 — 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-32407 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