dbcve.org
IpadosOperating system · Apple

CVE-2022-46703

MEDIUM · 5.5 CVSS v3.1 Published 2023-04-10
Fix available
A fix is available. Upgrade to 13.1 / 15.7.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 restrictions. This issue is fixed in iOS 15.7.2 and iPadOS 15.7.2, macOS Ventura 13.1, iOS 16.2 and iPadOS 16.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 · high confidence

A logic flaw in Apple's platform allowed applications to bypass location privacy restrictions, enabling unauthorized access to sensitive user location information. The vulnerability was addressed with improved restrictions in the specified iOS, iPadOS, and macOS versions.

MitigationUpdate affected devices to iOS 15.7.2/16.2, iPadOS 15.7.2/16.2, or macOS Ventura 13.1 or later to apply the fixed logic restrictions that 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.2>= 15.0, < 15.7.2
Iphone OsOperating system
Affected:< 16.2>= 15.0, < 15.7.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. Identify your Apple device type
    Determine whether the device is an iPhone, iPad, or Mac. On mobile devices, check Settings > General > About > Model Name. On Macs, click the Apple menu > About This Mac.
    Affected if Device must be an iPhone, iPad, or Mac running the affected operating systems
  2. Check iOS or iPadOS version on iPhone/iPad
    Go to Settings > General > About > Version to view the installed iOS or iPadOS version number.
    Affected if Version is 15.0 through 15.7.1 (less than 15.7.2) or any version before 16.2 (15.x versions that are not 15.7.2 or later, or versions below 16.2)
  3. Check macOS version on Mac
    Click the Apple menu > About This Mac to view the installed macOS version.
    Affected if Version is any release earlier than 13.1 (such as 13.0, 12.x, 11.x, etc.)
  4. Confirm location services are in use
    Go to Settings > Privacy & Security > Location Services (iOS/iPadOS) or System Settings > Privacy & Security > Location Services (macOS) to verify if Location Services are enabled.
    Affected if Location Services are enabled and the device runs an affected OS version, allowing the logic flaw to potentially expose location data to unauthorized apps

You are affected if you have an iPhone, iPad, or Mac running iOS/iPadOS versions 15.0 to 15.7.1 or below 16.2, or macOS versions below 13.1, with Location Services enabled.

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

Update affected devices to iOS 15.7.2/16.2, iPadOS 15.7.2/16.2, or macOS Ventura 13.1 or later to apply the fixed logic restrictions that prevent unauthorized location data access.

Recommended fix High confidence

iOS 15.7.2, iOS 16.2, iPadOS 15.7.2, iPadOS 16.2, macOS Ventura 13.1

  1. Determine the current iOS/iPadOS version on the device by going to Settings > General > About
  2. For iOS 15.x devices: Update to iOS 15.7.2 by going to Settings > General > Software Update
  3. For iOS 16.x devices: Update to iOS 16.2 by going to Settings > General > Software Update
  4. For iPadOS 15.x devices: Update to iPadOS 15.7.2 by going to Settings > General > Software Update
  5. For iPadOS 16.x devices: Update to iPadOS 16.2 by going to Settings > General > Software Update
  6. For macOS devices: Update to macOS Ventura 13.1 via System Preferences > Software Update

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-2022-46703 — 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-46703 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