CVE-2023-32403
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 · uneditedThis issue was addressed with improved redaction of sensitive information. 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 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 · high confidenceA vulnerability in multiple Apple operating systems allows a malicious application to bypass privacy protections and read sensitive location information that should have been redacted. The issue stems from insufficient data sanitization in the system's handling of location data.
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< 15.7.6>= 16.0, < 16.5< 15.7.6>= 16.0, < 16.5>= 11.0, < 11.7.7>= 12.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.
-
Determine iOS or iPadOS version on Apple mobile devicesOn the device, go to Settings > General > About and note the version number displayed next to 'Version'Affected if The version is less than 15.7.6, or greater than or equal to 16.0 but less than 16.5
-
Determine macOS version on Apple computersClick the Apple menu > About This Mac, or open Terminal and run the command 'sw_vers -productVersion'Affected if The version is 11.0 or higher but less than 11.7.7, or 12.0 or higher but less than 12.6.6, or 13.0 or higher but less than 13.4
-
Determine tvOS version on Apple TV devicesGo to Settings > General > About on the Apple TV and note the version numberAffected if The version is less than 16.5
-
Determine watchOS version on Apple Watch devicesOn Apple Watch, go to Settings > General > About. Alternatively, open the Watch app on a paired iPhone and check About under the watch nameAffected if The version is less than 9.5
A device is affected if its installed Apple operating system version falls within any of the vulnerable ranges listed for iOS, iPadOS, macOS, tvOS, or watchOS.
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 appropriate security update for the affected Apple operating system (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, or tvOS 16.5) to devices within the organization.
iOS 15.7.6/16.5, iPadOS 15.7.6/16.5, macOS 11.7.7/12.6.6/13.4, tvOS 16.5, or watchOS 9.5 (select based on device)
- For iOS devices: Upgrade to iOS 15.7.6 or iOS 16.5 (depending on device compatibility)
- For iPadOS devices: Upgrade to iPadOS 15.7.6 or iPadOS 16.5 (depending on device compatibility)
- For macOS Big Sur (11.x): Upgrade to macOS 11.7.7
- For macOS Monterey (12.x): Upgrade to macOS 12.6.6
- For macOS Ventura (13.x): Upgrade to macOS 13.4
- For Apple TV: Upgrade to tvOS 16.5
- For Apple Watch: Upgrade to watchOS 9.5
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-32403 — 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-32403 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