dbcve.org
IpadosOperating system · Apple

CVE-2023-42922

MEDIUM · 5.5 CVSS v3.1 Published 2023-12-12
Fix available
A fix is available. Upgrade to 12.7.2 / 13.6.3 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
This issue was addressed with improved redaction of sensitive information. This issue is fixed in macOS Sonoma 14.2, iOS 17.2 and iPadOS 17.2, macOS Ventura 13.6.3, iOS 16.7.3 and iPadOS 16.7.3, macOS Monterey 12.7.2. 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 · low confidence

A privacy vulnerability in Apple operating systems allowed an application to read sensitive location information due to improper redaction. The issue stemmed from insufficient protection of location data that should have been hidden or redacted before being accessible to applications.

MitigationApply the relevant OS updates: macOS Sonoma 14.2, iOS 17.2/iPadOS 17.2, macOS Ventura 13.6.3, iOS 16.7.3/iPadOS 16.7.3, or macOS Monterey 12.7.2 depending on the deployed platform.

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.7.3>= 17.0, < 17.2
Iphone OsOperating system
Affected:< 16.7.3>= 17.0, < 17.2
macOSOperating system
Affected:>= 12.0.0, < 12.7.2>= 13.0, < 13.6.3>= 14.0, < 14.2

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. Check iOS or iPadOS version on Apple mobile devices
    On the device, go to Settings > General > About and look at the 'Version' field. Alternatively, connect the device to a computer with iTunes or Finder and check the device summary page for the software version.
    Affected if The version number is less than 16.7.3, OR is 17.0 or higher but less than 17.2
  2. Check macOS version on Apple computers
    Click the Apple menu > About This Mac, or open Terminal and run 'sw_vers' to display the marketing version number.
    Affected if The version is 12.0.0 through 12.7.1, OR 13.0 through 13.6.2, OR 14.0 through 14.1 (inclusive on the lower end, exclusive on the upper end in each range)
  3. Confirm location services availability
    On iOS/iPadOS: go to Settings > Privacy & Security > Location Services and verify the feature is available. On macOS: go to System Settings > Privacy & Security > Location Services and check if the service is present.
    Affected if Location Services is present and enabled on the device (the vulnerability allows improperly redacted location data to be read by any authorized app)

A device is affected if it runs any iOS/iPadOS version in the ranges 16.7.3 to 17.1.x or 17.0 to 17.1.x, or any macOS version in the ranges 12.0.0-12.7.1, 13.0-13.6.2, or 14.0-14.1, and has location-based functionality available.

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 12.7.2 / 13.6.3 / 14.2 or later
Fixed in 12.7.213.6.314.2
Interim mitigation

Apply the relevant OS updates: macOS Sonoma 14.2, iOS 17.2/iPadOS 17.2, macOS Ventura 13.6.3, iOS 16.7.3/iPadOS 16.7.3, or macOS Monterey 12.7.2 depending on the deployed platform.

Recommended fix High confidence

iOS 16.7.3 or iOS 17.2 / iPadOS 16.7.3 or iPadOS 17.2 / macOS 12.7.2 / 13.6.3 / 14.2

  1. Identify the current OS version on the affected device (iPhone, iPad, or Mac)
  2. Back up important data on the device
  3. For iPhone/iPad: Go to Settings > General > Software Update and upgrade to iOS 16.7.3 (if currently on 16.x) or iOS 17.2 (if currently on 17.0-17.1)
  4. For iPad: Go to Settings > General > Software Update and upgrade to iPadOS 16.7.3 (if currently on 16.x) or iPadOS 17.2 (if currently on 17.0-17.1)
  5. For Mac: Open System Settings > General > Software Update and upgrade to macOS Monterey 12.7.2, Ventura 13.6.3, or Sonoma 14.2 depending on your current macOS version
  6. Verify the update was successfully installed by checking the OS version in Settings
Caveat Standard upgrade risks apply - review release notes for any behavioral changes before updating

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-42922 — 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-42922 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