CVE-2022-46692
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 logic issue was addressed with improved state management. This issue is fixed in Safari 16.2, tvOS 16.2, iCloud for Windows 14.1, iOS 15.7.2 and iPadOS 15.7.2, macOS Ventura 13.1, iOS 16.2 and iPadOS 16.2, watchOS 9.2. Processing maliciously crafted web content may bypass Same Origin Policy.
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 confidenceA logic error in state management allows malicious web content to bypass Same Origin Policy (SOP) protections in Safari and WebKit-based browsers on Apple devices. An attacker would need to lure a user into visiting a specially crafted malicious webpage to exploit this vulnerability, potentially allowing unauthorized access to data from other origins.
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< 16.2< 14.1< 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/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.
-
Identify the Apple browser or OS productDetermine if the device runs Safari, iOS, iPadOS, macOS, tvOS, watchOS, or iCloud for Windows. For iOS/iPadOS check Settings > General > About; for macOS check System Settings > About This Mac; for Safari open Safari and choose Safari > About Safari; for iCloud for Windows check the installed version in Programs and Features.Affected if The product is Safari, iOS, iPadOS, macOS, tvOS, watchOS, or iCloud for Windows.
-
Check the installed Safari versionOpen Safari and select Safari > About Safari. Note the version number displayed (e.g., 16.1, 16.0, 15.7.1).Affected if Safari version is lower than 16.2.
-
Check the installed iOS or iPadOS versionOpen Settings > General > About on the iPhone or iPad. Note the version number (e.g., 16.1, 16.0, 15.7.1).Affected if iOS or iPadOS version is lower than 15.7.2, or is 16.0 to 16.1 (less than 16.2).
-
Check the installed macOS versionOpen System Settings (or System Preferences on older versions) > General > About This Mac. Note the macOS version (e.g., 13.0, 12.x).Affected if macOS version is lower than 13.1.
-
Check the installed tvOS or watchOS versionOn Apple TV go to Settings > General > About > Version. On Apple Watch go to Settings > General > About > Version. Note the version number.Affected if tvOS version is lower than 16.2, or watchOS version is lower than 9.2.
-
Check iCloud for Windows versionOpen the iCloud app or check Programs and Features in Control Panel. Note the installed version.Affected if iCloud for Windows version is lower than 14.1.
The environment is affected if the installed Safari, iOS, iPadOS, macOS, tvOS, watchOS, or iCloud for Windows version falls within the affected ranges (Safari < 16.2, iOS/iPadOS < 15.7.2 or >= 16.0 and < 16.2, macOS < 13.1, tvOS < 16.2, watchOS < 9.2, iCloud for Windows < 14.1).
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.114.1
Apply the vendor-supplied updates (Safari 16.2, iOS/iPadOS 15.7.2+ or 16.2+, macOS Ventura 13.1+, watchOS 9.2+, tvOS 16.2+, iCloud for Windows 14.1+) to patched versions. For enterprise environments, deploy updates via MDM or software distribution tools and verify compliance.
Minimum fixed versions: Safari 16.2, tvOS 16.2, iCloud for Windows 14.1, iOS 15.7.2/16.2, iPadOS 15.7.2/16.2, macOS Ventura 13.1, watchOS 9.2
- For iOS devices: Upgrade to iOS 15.7.2 or iOS 16.2 via Settings > General > Software Update
- For iPadOS devices: Upgrade to iPadOS 15.7.2 or iPadOS 16.2 via Settings > General > Software Update
- For macOS: Upgrade to macOS Ventura 13.1 via System Preferences > Software Update
- For Safari (standalone): Upgrade to Safari 16.2 through macOS update or Software Update
- For tvOS devices: Upgrade to tvOS 16.2 via Settings > General > Software Update
- For Apple Watch: Upgrade to watchOS 9.2 via the Watch app on iPhone > General > Software Update
- For iCloud for Windows: Upgrade to iCloud 14.1 via the Microsoft Store or Apple website
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-46692 — 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-46692 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