dbcve.org
IpadosOperating system · Apple

CVE-2023-32399

MEDIUM · 5.5 CVSS v3.1 Published 2023-06-23
Fix available
A fix is available. Upgrade to 9.5 / 13.4 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
The issue was addressed with improved handling of caches. This issue is fixed in iOS 16.5 and iPadOS 16.5, watchOS 9.5, tvOS 16.5, macOS Ventura 13.4. 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 confidence

A vulnerability in Apple's mobile and desktop operating systems allows a malicious or compromised application to read sensitive location information due to improper cache handling. The vulnerability exists in iOS, iPadOS, watchOS, tvOS, and macOS prior to the fixed versions.

MitigationApply the available security updates: iOS 16.5 and iPadOS 16.5, watchOS 9.5, tvOS 16.5, or macOS Ventura 13.4. Ensure all devices are updated to the patched versions to prevent unauthorized location data 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
IpadosOperating system
Affected:< 16.5
Iphone OsOperating system
Affected:< 16.5
macOSOperating system
Affected:>= 13.0, < 13.4
TvosOperating system
Affected:< 16.5
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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Apple device and operating system
    Determine whether the device runs iOS (iPhone), iPadOS (iPad), macOS (Mac), tvOS (Apple TV), or watchOS (Apple Watch). This can be done via Settings > General > About on iOS/iPadOS/watchOS, System Settings or System Preferences on macOS, or the Settings app on tvOS.
    Affected if The device runs any of the affected Apple operating systems (iOS, iPadOS, macOS, tvOS, watchOS)
  2. Check the installed iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About and look at the 'Version' field. Note the full version number (e.g., 16.4.1).
    Affected if The device runs iOS or iPadOS versions earlier than 16.5 (e.g., 16.4, 16.3, etc.)
  3. Check the installed macOS version
    On Mac, go to System Settings > General > About (or System Preferences > About on older macOS) and look at the 'macOS' or 'Version' field. Note the full version number (e.g., 13.3).
    Affected if The Mac runs macOS Ventura version 13.0 through 13.3 (versions 13.0 <= version < 13.4)
  4. Check the installed watchOS or tvOS version
    On Apple Watch, open the Watch app on iPhone, go to General > About, and check the 'watchOS' version. On Apple TV, go to Settings > General > About and check the 'tvOS' version.
    Affected if The device runs watchOS earlier than 9.5 or tvOS earlier than 16.5

A user is affected if their Apple device runs an operating system version that falls within the vulnerable ranges: iOS/iPadOS/tvOS/watchOS < 16.5 or macOS 13.0 to 13.3.

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 / 13.4 / 16.5 or later
Fixed in 9.513.416.5
Interim mitigation

Apply the available security updates: iOS 16.5 and iPadOS 16.5, watchOS 9.5, tvOS 16.5, or macOS Ventura 13.4. Ensure all devices are updated to the patched versions to prevent unauthorized location data access.

Recommended fix High confidence

iOS 16.5, iPadOS 16.5, watchOS 9.5, tvOS 16.5, macOS Ventura 13.4

  1. For iPhone users: Upgrade to iOS 16.5 or later via Settings > General > Software Update
  2. For iPad users: Upgrade to iPadOS 16.5 or later via Settings > General > Software Update
  3. For Apple Watch users: Upgrade to watchOS 9.5 or later via the Watch app on iPhone > General > Software Update
  4. For Apple TV users: Upgrade to tvOS 16.5 or later via Settings > General > Apple TV Software Update
  5. For Mac users: Upgrade to macOS Ventura 13.4 or later via System Settings > General > Software Update
Caveat Standard Apple OS updates may include minor UI changes or deprecate older features; backup before upgrading recommended

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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