CVE-2023-32392
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 · uneditedA privacy issue was addressed with improved private data redaction for log entries. This issue is fixed in watchOS 9.5, 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 read sensitive location information.
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 confidenceA privacy vulnerability existed in multiple Apple operating systems where log entries contained sensitive location information that was not properly redacted, potentially allowing malicious apps to access this sensitive data through log file access.
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< 16.5< 16.5>= 11.0, < 11.7.7>= 12.0.0, < 12.6.6>= 13.0, < 13.4< 16.5< 9.5CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Apple operating systemDetermine which Apple OS is running on the device: iOS (iPhone), iPadOS (iPad), macOS (Mac), tvOS (Apple TV), or watchOS (Apple Watch). This can be done through Settings > General > About on iOS/iPadOS, System Settings > About This Mac on macOS, or Settings > General on tvOS/watchOS.Affected if The device is running any of the affected Apple operating systems (iOS, iPadOS, macOS, tvOS, or watchOS).
-
Check iOS or iPadOS versionOn iPhone or iPad, go to Settings > General > About and note the version number (for example, 16.4).Affected if The version is less than 16.5 (for example, 16.4, 16.3, 15.x, etc.).
-
Check macOS versionOn Mac, click the Apple menu > About This Mac and note the version number (for example, 13.3). Also note the build number if displayed.Affected if The version is 11.0 or higher but less than 11.7.7, OR 12.0.0 or higher but less than 12.6.6, OR 13.0 or higher but less than 13.4.
-
Check tvOS or watchOS versionOn Apple TV, go to Settings > General > About > Version. On Apple Watch, open the Watch app on paired iPhone > General > About > watchOS Version.Affected if The version is less than 16.5 for tvOS, or less than 9.5 for watchOS.
-
Assess log file access exposureThis vulnerability allows malicious apps with log file access to potentially read location information that was improperly redacted. Check if third-party apps have been granted access to system logs or if the device has been jailbroken/rooted which could allow unauthorized log access.Affected if The device runs a vulnerable OS version AND has apps or tools that can access system log files.
A user is affected if their device runs iOS, iPadOS, tvOS, or watchOS before version 16.5/9.5, or macOS before 11.7.7/12.6.6/13.4, AND a malicious app can access system log files.
Generated from the published advisory. Verify against your own configuration.
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 · scoped9.511.7.712.6.6
Apply the vendor patches by updating to iOS 16.5/iPadOS 16.5, macOS Ventura 13.4/macOS Big Sur 11.7.7/macOS Monterey 12.6.6, watchOS 9.5, or tvOS 16.5 or later.
iOS 16.5, iPadOS 16.5, macOS 11.7.7 (Big Sur), macOS 12.6.6 (Monterey), macOS 13.4 (Ventura), tvOS 16.5, watchOS 9.5
- Verify current device iOS/iPadOS version by going to Settings > General > About
- If running iOS/iPadOS < 16.5, back up important data using iCloud or computer backup
- Connect device to power and WiFi, then go to Settings > General > Software Update
- Download and install iOS 16.5 or iPadOS 16.5
- For macOS: Go to System Settings > General > Software Update and install the appropriate fixed version (11.7.7 for Big Sur, 12.6.6 for Monterey, 13.4 for Ventura)
- For Apple Watch: Open the Watch app on iPhone, go to General > Software Update and install watchOS 9.5
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 16.5
- After update, verify the new version is installed by checking Settings > General > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-32392 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-32392 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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