dbcve.org
IpadosOperating system · Apple

CVE-2022-46710

MEDIUM · 5.5 CVSS v3.1 Published 2024-01-10
Fix available
A fix is available. Upgrade to 13.1 / 16.2 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
A logic issue was addressed with improved checks. This issue is fixed in iOS 16.2 and iPadOS 16.2, macOS Ventura 13.1. Location data may be shared via iCloud links even if Location metadata is disabled via the Share Sheet.

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 logic flaw in the iOS/macOS Share Sheet allowed location metadata to be inadvertently included in iCloud shared links even when users explicitly disabled the Location toggle in the Share Sheet. This bypassed user privacy settings and caused location data to be exposed through shared links.

MitigationUpdate affected devices to iOS 16.2+, iPadOS 16.2+, or macOS Ventura 13.1+ to receive Apple's logic fix that enforces the user's location metadata preference.

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.2
Iphone OsOperating system
Affected:< 16.2
macOSOperating system
Affected:< 13.1

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 version on iPhone or iPad
    Go to Settings > General > About > Version and compare the displayed version number to the affected range (versions below 16.2)
    Affected if Device is running iOS < 16.2 or iPadOS < 16.2 and uses Share Sheet to create iCloud shared links
  2. Check macOS version on Mac
    Click Apple menu > About This Mac and look at the macOS version number, or run 'sw_vers' in Terminal
    Affected if Device is running macOS < 13.1 and uses Share Sheet to create iCloud shared links
  3. Identify Share Sheet usage with iCloud sharing
    Review recent sharing activity - determine if the Share Sheet was used to create iCloud shared links (via Files app, Photos, or other apps that support iCloud sharing)
    Affected if User has created iCloud shared links while on an affected OS version regardless of Location toggle setting in Share Sheet
  4. Verify location metadata exposure in existing shared links
    Inspect existing iCloud shared links - some third-party tools or iCloud web interface may reveal whether location metadata is attached to shared items
    Affected if Location metadata is present in shared links that were created with the Location toggle disabled in Share Sheet while on an affected OS version

User is affected if running iOS < 16.2, iPadOS < 16.2, or macOS < 13.1 AND has used Share Sheet to create iCloud shared links, regardless of whether the Location toggle was explicitly disabled.

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 13.1 / 16.2 or later
Fixed in 13.116.2
Interim mitigation

Update affected devices to iOS 16.2+, iPadOS 16.2+, or macOS Ventura 13.1+ to receive Apple's logic fix that enforces the user's location metadata preference.

Recommended fix High confidence

iOS 16.2 / iPadOS 16.2 / macOS Ventura 13.1 or later

  1. Back up your device data before performing any OS upgrade
  2. On iPhone or iPad: Go to Settings > General > Software Update and install iOS 16.2 or iPadOS 16.2
  3. On Mac: Go to System Settings > General > Software Update and install macOS Ventura 13.1
  4. After upgrade, verify the installed version in Settings > General > About
Caveat Standard OS upgrade risks apply - review app compatibility with new OS version before upgrading

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

Fix this in Ipados Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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