dbcve.org
SafariWeb browser · Apple

CVE-2022-46700

HIGH · 8.8 CVSS v3.1 Published 2022-12-15
Fix available
A fix is available. Upgrade to 9.2 / 15.7.2 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 input validation. This issue is fixed in Safari 16.2, 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. 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

Memory corruption vulnerability in WebKit (Apple's browser engine) that allows arbitrary code execution when processing maliciously crafted web content. The issue was addressed through improved input validation in the affected Apple operating systems and Safari.

MitigationApply vendor patches by updating to Safari 16.2, iOS/iPadOS 15.7.2 or later (or 16.2+), tvOS 16.2, watchOS 9.2, or macOS Ventura 13.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
IpadosOperating system
Affected:>= 15.0, < 15.7.2>= 16.0, < 16.2
Iphone OsOperating system
Affected:>= 15.0, < 15.7.2>= 16.0, < 16.2
macOSOperating system
Affected:= 13.0
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 Apple platform and Safari browser version
    On macOS: Click Safari > About Safari to see the version number. On iOS/iPadOS: Go to Settings > Safari > About to see the version.
    Affected if Safari version is earlier than 16.2 on any platform
  2. Check macOS version if running Safari on Mac
    Click Apple menu > About This Mac to view the macOS version number.
    Affected if macOS version is 13.0 (Ventura)
  3. Check iOS or iPadOS version on iPhone or iPad
    Go to Settings > General > About to view the iOS/iPadOS version number.
    Affected if iOS/iPadOS version is 15.0 to 15.7.2 or 16.0 to 16.2
  4. Check tvOS version on Apple TV
    Go to Settings > General > About TV > Version to see the tvOS version.
    Affected if tvOS version is earlier than 16.2
  5. Check watchOS version on Apple Watch
    Open the Watch app on iPhone, go to General > About to view the watchOS version.
    Affected if watchOS version is earlier than 9.2

A user is affected if they are running any unpatched Safari, iOS, iPadOS, macOS 13.0, tvOS, or watchOS version within the specified vulnerable ranges and use Safari or WebKit-based browsers to process untrusted web content.

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

Apply vendor patches by updating to Safari 16.2, iOS/iPadOS 15.7.2 or later (or 16.2+), tvOS 16.2, watchOS 9.2, or macOS Ventura 13.1.

Recommended fix High confidence

Upgrade to Safari 16.2, tvOS 16.2, macOS Ventura 13.1, iOS/iPadOS 15.7.2, iOS/iPadOS 16.2, or watchOS 9.2 depending on device type

  1. Identify the Apple device and current OS version (Safari, iOS, iPadOS, macOS, tvOS, or watchOS)
  2. For iOS/iPadOS 15.x: Upgrade to version 15.7.2 via Settings > General > Software Update
  3. For iOS/iPadOS 16.x: Upgrade to version 16.2 via Settings > General > Software Update
  4. For macOS 13.0: Upgrade to macOS Ventura 13.1 via System Settings > Software Update
  5. For Safari: Upgrade to Safari 16.2 through macOS software update
  6. For tvOS: Upgrade to tvOS 16.2 via Settings > System > Software Update
  7. For watchOS: Upgrade to watchOS 9.2 via the Watch app on iPhone
  8. Ensure the device is connected to power and Wi-Fi during the update process
Caveat Standard Apple minor version updates typically do not introduce breaking changes; however, verify app compatibility with the new OS version after upgrading

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

Fix this in Safari Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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