dbcve.org
IpadosOperating system · Apple

CVE-2023-32388

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 privacy issue was addressed with improved private data redaction for log entries. This issue is fixed in watchOS 9.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

This vulnerability allows an application to bypass Privacy preferences due to insufficient private data redaction in log entries. The issue could expose sensitive user information through logs that should have been redacted, violating privacy settings.

MitigationApply the appropriate Apple OS updates (watchOS 9.5, macOS Ventura 13.4, iOS/iPadOS 15.7.6 or 16.5, macOS Big Sur 11.7.7, macOS Monterey 12.6.6) to affected devices to ensure proper log redaction is enforced.

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.0, < 12.6.6>= 13.0, < 13.4
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
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 iPadOS version
    Go to Settings > General > About on the iPad and note the version number. Compare it to the affected ranges: < 15.7.6 or >= 16.0 and < 16.5
    Affected if The installed version falls within < 15.7.6 or >= 16.0 and < 16.5
  2. Check iPhone iOS version
    Go to Settings > General > About on the iPhone and note the version number. Compare it to the affected ranges: < 15.7.6 or >= 16.0 and < 16.5
    Affected if The installed version falls within < 15.7.6 or >= 16.0 and < 16.5
  3. Check macOS version
    Click the Apple menu > About This Mac and note the version number. Compare to affected ranges: >= 11.0 and < 11.7.7, >= 12.0.0 and < 12.6.6, or >= 13.0 and < 13.4
    Affected if The installed version falls within any of the three affected macOS ranges
  4. Check watchOS version
    Open the Watch app on paired iPhone, go to My Watch > General > About and note the version. Compare to affected range: < 9.5
    Affected if The installed watchOS version is less than 9.5
  5. Verify Privacy settings and logging
    Check if Privacy preferences are enabled in System Preferences (macOS) or Settings (iOS/iPadOS/watchOS) while the device runs an affected version. The vulnerability triggers when privacy settings should redact certain data from logs but fail to do so.
    Affected if Privacy preferences that should redact sensitive data are active on a device running an affected OS version

A user is affected if their device runs any iPadOS, iOS, macOS, or watchOS version within the specified vulnerable ranges and uses privacy settings that rely on log redaction.

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 appropriate Apple OS updates (watchOS 9.5, macOS Ventura 13.4, iOS/iPadOS 15.7.6 or 16.5, macOS Big Sur 11.7.7, macOS Monterey 12.6.6) to affected devices to ensure proper log redaction is enforced.

Recommended fix High confidence

iOS 15.7.6/16.5+, iPadOS 15.7.6/16.5+, macOS 11.7.7/12.6.6/13.4+, watchOS 9.5+

  1. Back up your device data before upgrading
  2. For iPhone/iPad: Upgrade to iOS/iPadOS 15.7.6 or iOS/iPadOS 16.5 and later
  3. For macOS: Upgrade to macOS Big Sur 11.7.7, macOS Monterey 12.6.6, or macOS Ventura 13.4 and later
  4. For Apple Watch: Upgrade to watchOS 9.5 and later
  5. After upgrading, verify the system reports the updated version
Caveat Standard OS upgrade considerations apply - ensure app compatibility and back up data before upgrading

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-2023-32388 — 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-32388 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