dbcve.org
IpadosOperating system · Apple

CVE-2022-46718

MEDIUM · 5.5 CVSS v3.1 Published 2023-06-23
Fix available
A fix is available. Upgrade to 11.7.2 / 12.6.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, macOS Big Sur 11.7.2, macOS Monterey 12.6.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 iOS, iPadOS, and macOS allowed applications to bypass location access restrictions and read sensitive location information that should have been protected by system policies. The vulnerability stemmed from insufficient authorization checks in the operating system's location services framework.

MitigationApply the vendor-supplied patches by updating affected devices to iOS 15.7.2 or later, iPadOS 15.7.2 or later, macOS Ventura 13.1 or later, macOS Monterey 12.6.2 or later, or macOS Big Sur 11.7.2 or later.

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:< 15.7.2
Iphone OsOperating system
Affected:< 15.7.2
macOSOperating system
Affected:>= 11.0.0, < 11.7.2>= 12.0.0, < 12.6.2>= 13.0, < 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
    Go to Settings > General > About and note the version number under 'Version'
    Affected if The version is earlier than 15.7.2 (e.g., 15.7.1, 15.6, 15.5, etc.)
  2. Check iPadOS version on iPad
    Go to Settings > General > About and note the version number under 'Version'
    Affected if The version is earlier than 15.7.2 (e.g., 15.7.1, 15.6, 15.5, etc.)
  3. Check macOS version
    Click the Apple menu > About This Mac and note the version number (e.g., 13.0, 12.5, 11.7.1)
    Affected if The version falls within any of these ranges: 11.0.0 to 11.7.1, 12.0.0 to 12.6.1, or 13.0 to 13.0 (all versions before the fixed releases)
  4. Verify Location Services status
    On iOS/iPadOS: Settings > Privacy & Security > Location Services; On macOS: System Settings > Privacy & Security > Location Services
    Affected if Location Services is enabled and the device runs a vulnerable OS version listed above

A user is affected if their device runs iOS/iPadOS below 15.7.2 or macOS below 11.7.2/12.6.2/13.1 and has Location Services enabled, allowing potentially untrusted apps to access location data beyond what policy should permit.

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 11.7.2 / 12.6.2 / 13.1 or later
Fixed in 11.7.212.6.213.1
Interim mitigation

Apply the vendor-supplied patches by updating affected devices to iOS 15.7.2 or later, iPadOS 15.7.2 or later, macOS Ventura 13.1 or later, macOS Monterey 12.6.2 or later, or macOS Big Sur 11.7.2 or later.

Recommended fix High confidence

iOS 15.7.2 / iPadOS 15.7.2 / macOS Big Sur 11.7.2 / macOS Monterey 12.6.2 / macOS Ventura 13.1

  1. Identify the device type (iPhone, iPad, or Mac)
  2. For iPhone/iPad: Go to Settings > General > Software Update and install iOS 15.7.2 / iPadOS 15.7.2
  3. For Mac: Go to System Settings > General > Software Update (or System Preferences > Software Update) and install the appropriate fixed version
  4. Ensure the device is connected to power and Wi-Fi before starting the update
  5. After installation, verify the update was successful by checking Settings > General > About
Caveat Apple updates typically do not introduce breaking changes for end users; however, some older applications may become incompatible

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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