dbcve.org
SafariWeb browser · Apple

CVE-2022-46699

HIGH · 8.8 CVSS v3.1 Published 2022-12-15
Fix available
A fix is available. Upgrade to 9.2 / 13.1 or later.
See remediation →
95/100
Remediation priority · Urgent
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 memory corruption issue was addressed with improved state management. This issue is fixed in Safari 16.2, tvOS 16.2, macOS Ventura 13.1, iOS 16.2 and iPadOS 16.2, watchOS 9.2. Processing maliciously crafted web content may lead to arbitrary code execution.

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 memory corruption vulnerability in WebKit (Apple's browser engine) allows arbitrary code execution when processing maliciously crafted web content. The issue was addressed through improved state management, indicating a flaw in how the browser handled internal state during web page processing.

MitigationApply vendor-supplied patches for the affected Apple products (iOS 16.2+, iPadOS 16.2+, macOS Ventura 13.1+, watchOS 9.2+, Safari 16.2+, tvOS 16.2+) or disable JavaScript in Safari/browser until patching is possible.

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
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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 the WebKit-based browser or app
    Determine if you are using Safari, or any iOS/macOS app that embeds WebKit (such as third-party browsers, email clients with HTML rendering, or other apps that display web content)
    Affected if The device runs any Apple operating system with a WebKit-based browser or component
  2. Check Safari version on macOS
    Open Safari, click Safari > About Safari, and note the version number displayed
    Affected if The version is earlier than 16.2 (e.g., 16.1, 16.0, 15.x)
  3. Check iOS or iPadOS Safari version
    Go to Settings > Safari > About, or Settings > General > About, and note the version number
    Affected if The iOS version is earlier than 16.2 or the iPadOS version is earlier than 16.2
  4. Check macOS version for built-in WebKit
    Open System Settings > General > About, or click Apple menu > About This Mac, and note the macOS version
    Affected if The macOS version is earlier than 13.1 (such as 13.0, 12.x, 11.x)
  5. Verify JavaScript is enabled in Safari
    In Safari, go to Safari > Settings > Security (or Preferences > Security) and check if 'Enable JavaScript' is checked; on iOS, go to Settings > Safari > Advanced and check if JavaScript is enabled
    Affected if JavaScript is currently enabled (the exploit requires JavaScript to process malicious web content)

You are affected if you run any WebKit-based browser on an Apple device with a version lower than Safari 16.2 / iPadOS 16.2 / iOS 16.2 / macOS 13.1 / tvOS 16.2 / watchOS 9.2 AND JavaScript is enabled in that browser.

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

Apply vendor-supplied patches for the affected Apple products (iOS 16.2+, iPadOS 16.2+, macOS Ventura 13.1+, watchOS 9.2+, Safari 16.2+, tvOS 16.2+) or disable JavaScript in Safari/browser until patching is possible.

Recommended fix High confidence

Upgrade to iOS/iPadOS 16.2, macOS Ventura 13.1, tvOS 16.2, watchOS 9.2, and Safari 16.2 as appropriate for your device

  1. Back up all important data on the device before upgrading
  2. For iOS/iPadOS devices: Go to Settings > General > Software Update, then download and install iOS/iPadOS 16.2
  3. For macOS: Go to System Settings (or System Preferences) > Software Update, then download and install macOS Ventura 13.1
  4. For tvOS: Go to Settings > System > Software Update, then download and install tvOS 16.2
  5. For watchOS: Open the Watch app on iPhone, go to My Watch > General > Software Update, or go to Settings on the watch and install watchOS 9.2
  6. Safari will be updated automatically as part of iOS/iPadOS 16.2 or macOS Ventura 13.1 updates
  7. After updating, verify the version in Settings > General > About (iOS/iPadOS) or System Settings > About This Mac (macOS)
Caveat Standard OS upgrade considerations apply: ensure backup of data, verify app compatibility with new OS version before proceeding

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

Fix this in Safari Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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