dbcve.org
SafariWeb browser · Apple

CVE-2022-46698

MEDIUM · 6.5 CVSS v3.1 Published 2022-12-15
Fix available
A fix is available. Upgrade to 9.2 / 13.1 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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 Safari 16.2, tvOS 16.2, iCloud for Windows 14.1, macOS Ventura 13.1, iOS 16.2 and iPadOS 16.2, watchOS 9.2. Processing maliciously crafted web content may disclose sensitive user 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 · moderate confidence

A logic flaw in Apple's web content processing allows malicious web pages to bypass security checks and access sensitive user information. The vulnerability affects WebKit rendering engine components across Safari, iOS, iPadOS, macOS, tvOS, watchOS, and iCloud for Windows.

MitigationApply the vendor-supplied security updates: Safari 16.2, iOS/iPadOS 16.2, macOS Ventura 13.1, tvOS 16.2, watchOS 9.2, and iCloud for Windows 14.1.

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
SafariWeb browser
Affected:< 16.2
IcloudApplication
Affected:< 14.0
IpadosOperating system
Affected:< 16.2
Iphone OsOperating system
Affected:< 16.2
macOSOperating system
Affected:< 13.1
TvosOperating system
Affected:< 16.2
WatchosOperating system
Affected:< 9.2

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/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 installed Apple products
    Determine which Apple software is in use: Safari browser, iOS/iPadOS devices, macOS, tvOS, watchOS, or iCloud for Windows
    Affected if Any of these products are present on the system or device
  2. Check Safari version
    Open Safari, go to Safari menu > About Safari, and note the version number displayed
    Affected if Safari version is earlier than 16.2
  3. Check macOS version
    Click Apple menu > About This Mac, and note the macOS version shown
    Affected if macOS version is earlier than 13.1 (Ventura)
  4. Check iOS/iPadOS version
    On device, go to Settings > General > About, and note the iOS/iPadOS version
    Affected if iOS or iPadOS version is earlier than 16.2
  5. Check iCloud for Windows version
    Open iCloud, access Help > About, and note the version number
    Affected if iCloud for Windows version is earlier than 14.0

A user is affected if any of the installed Apple products (Safari, iOS, iPadOS, macOS, tvOS, watchOS, or iCloud for Windows) have a version lower than the fixed releases (Safari 16.2, iOS/iPadOS 16.2, macOS 13.1, tvOS 16.2, watchOS 9.2, iCloud 14.0).

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 9.2 / 13.1 / 14.0 or later
Fixed in 9.213.114.0
Interim mitigation

Apply the vendor-supplied security updates: Safari 16.2, iOS/iPadOS 16.2, macOS Ventura 13.1, tvOS 16.2, watchOS 9.2, and iCloud for Windows 14.1.

Recommended fix High confidence

Upgrade to Safari 16.2, iCloud for Windows 14.1, iOS 16.2, iPadOS 16.2, macOS Ventura 13.1, tvOS 16.2, or watchOS 9.2 depending on the affected product

  1. For iOS and iPadOS devices: Go to Settings > General > Software Update and install iOS 16.2 or iPadOS 16.2
  2. For macOS: Go to System Settings > General > Software Update and install macOS Ventura 13.1
  3. For tvOS: Go to Settings > System > Software Updates and install tvOS 16.2
  4. For watchOS: On iPhone, open Watch app, go to My Watch > General > Software Update and install watchOS 9.2
  5. For Safari: Update via macOS system update to Safari 16.2, or update macOS to 13.1 which includes the fixed Safari version
  6. For iCloud for Windows: Download and install iCloud for Windows 14.1 from Apple
Caveat Standard Apple OS updates may include feature changes; backup data before updating

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

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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 locally
dbcve dependency scanner

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