CVE-2022-46695
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 spoofing issue existed in the handling of URLs. This issue was addressed with improved input validation. This issue is fixed in tvOS 16.2, macOS Ventura 13.1, iOS 15.7.2 and iPadOS 15.7.2, iOS 16.2 and iPadOS 16.2, watchOS 9.2. Visiting a website that frames malicious content may lead to UI spoofing.
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 confidenceCVE-2022-46695 is a URL spoofing vulnerability in Apple's tvOS, macOS, iOS, iPadOS, and watchOS. The vulnerability stems from improper input validation when handling URLs, allowing malicious websites to frame content that can deceive users through UI spoofing. Attackers exploit this by crafting websites that present deceptive interface elements, potentially tricking users into believing they are interacting with legitimate content or applications.
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< 15.7.2>= 16.0, < 16.2< 15.7.2>= 16.0, < 16.2< 13.1< 16.2< 9.2CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 versionOn the iPhone or iPad, go to Settings > General > About and note the version number shown next to 'Version'Affected if The version is earlier than 15.7.2, or is 16.0, 16.1, or any version 16.x below 16.2
-
Check iPadOS versionOn the iPad, go to Settings > General > About and note the version number shown next to 'Version'Affected if The version is earlier than 15.7.2, or is 16.0, 16.1, or any version 16.x below 16.2
-
Check macOS versionClick the Apple menu in the top-left corner of the screen, select 'About This Mac', and note the version number under the macOS nameAffected if The version is earlier than 13.1 (any version of macOS Monterey or earlier)
-
Check tvOS versionOn Apple TV, go to Settings > General > About and note the version number shown next to 'Version'Affected if The version is earlier than 16.2
-
Check watchOS versionOn the paired iPhone, open the Watch app, go to My Watch > General > About, and note the version numberAffected if The version is earlier than 9.2
A device is affected if it runs any of these operating systems at a version lower than the fixed release (iOS/iPadOS 15.7.2 or 16.2+, macOS 13.1+, tvOS 16.2+, watchOS 9.2+) and if users may visit untrusted websites via Safari or other browsers.
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.213.115.7.2
Deploy the vendor-provided security updates (tvOS 16.2, macOS Ventura 13.1, iOS/iPadOS 15.7.2 or 16.2, watchOS 9.2 or later) to all affected devices. Implement patch management procedures to ensure timely updates across the organization.
iOS 15.7.2, iOS 16.2, iPadOS 15.7.2, iPadOS 16.2, macOS Ventura 13.1, tvOS 16.2, or watchOS 9.2 (depending on device type)
- Identify the current version of the affected Apple device (iPhone, iPad, Mac, Apple TV, or Apple Watch)
- Determine which operating system is running (iOS, iPadOS, macOS, tvOS, or watchOS)
- For iPhone/iPad on iOS/iPadOS 15.x: upgrade to iOS/iPadOS 15.7.2
- For iPhone/iPad on iOS/iPadOS 16.x: upgrade to iOS/iPadOS 16.2
- For Mac: upgrade to macOS Ventura 13.1
- For Apple TV: upgrade to tvOS 16.2
- For Apple Watch: upgrade to watchOS 9.2
- Perform a backup of the device before upgrading, then install the update via Settings > General > Software Update (iOS/iPadOS/watchOS), System Preferences > Software Update (macOS), or Settings > General > Software Update (tvOS)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46695 — 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-46695 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