CVE-2022-32875
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 logic issue was addressed with improved state management. This issue is fixed in macOS Big Sur 11.7, macOS Ventura 13, iOS 16, watchOS 9, macOS Monterey 12.6. 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 logic flaw in state management allowed an application to bypass location privacy controls and access sensitive location information when it should not have been permitted to do so. The vulnerability stemmed from insufficient validation of application state before granting 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< 16.0>= 11.0, < 11.7>= 12.0, < 12.6< 9.0CVSS 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
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Check iOS version on iPhone or iPadGo to Settings > General > About on the iOS device and note the Version numberAffected if The version is less than 16.0 (for example, 15.x or earlier)
-
Check macOS version on MacClick the Apple menu > About This Mac and note the macOS version displayed (for example, 11.x or 12.x)Affected if The version is 11.0 to 11.6.x OR 12.0 to 12.5.x
-
Check watchOS version on Apple WatchOpen the Watch app on paired iPhone, go to General > About, and note the watchOS version; or on Apple Watch go to Settings > AboutAffected if The version is less than 9.0 (for example, 8.x or earlier)
The environment is affected if any Apple device (iPhone, iPad, Mac, or Apple Watch) is running an OS version that falls within the vulnerable ranges listed above.
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.011.712.6
Update to the patched versions: macOS Big Sur 11.7, macOS Monterey 12.6, macOS Ventura 13, iOS 16, or watchOS 9. Application developers should review their location permission handling to ensure compliance with the corrected state management model.
iOS 16+, watchOS 9+, macOS 11.7+, macOS 12.6+, or macOS 13+ (depending on device and compatibility)
- Determine the current installed OS version on the affected device (iPhone, Mac, or Apple Watch)
- For iPhone: Upgrade to iOS 16 or later via Settings > General > Software Update
- For Mac: Upgrade to macOS 11.7 (Big Sur) or macOS 12.6 (Monterey) or macOS 13 (Ventura) via System Preferences > Software Update
- For Apple Watch: Upgrade to watchOS 9 or later via the Watch app on iPhone > General > Software Update
- After upgrading, verify the device is running a patched version by checking Settings > General > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32875 — 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-2022-32875 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