dbcve.org
IpadosOperating system · Apple

CVE-2022-42813

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-01
Fix available
A fix is available. Upgrade to 9.1 / 13.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 certificate validation issue existed in the handling of WKWebView. This issue was addressed with improved validation. This issue is fixed in tvOS 16.1, iOS 16.1 and iPadOS 16, macOS Ventura 13, watchOS 9.1. Processing a maliciously crafted certificate 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 · moderate confidence

A certificate validation vulnerability exists in WKWebView (Apple's web view component) where maliciously crafted certificates are not properly validated, potentially allowing arbitrary code execution. The issue stems from inadequate certificate chain validation in the WebKit framework.

MitigationApply the vendor-supplied security updates (iOS 16.1+, iPadOS 16+, macOS Ventura 13+, tvOS 16.1+, watchOS 9.1+) to all affected devices. For third-party applications using WKWebView, ensure applications are rebuilt against updated SDKs and deployed to endpoint devices.

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
IpadosOperating system
Affected:< 16.0
Iphone OsOperating system
Affected:< 16.1
macOSOperating system
Affected:< 13.0
TvosOperating system
Affected:< 16.1
WatchosOperating system
Affected:< 9.1

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Check the device operating system version
    On iOS/iPadOS, go to Settings > General > About to view the version number. On macOS, click Apple menu > About This Mac. On tvOS/watchOS, go to Settings > General > About.
    Affected if The OS version is below iOS 16.1, iPadOS 16.0, macOS 13.0, tvOS 16.1, or watchOS 9.1.
  2. Identify applications using WKWebView
    Review application code or documentation for usage of WebKit's WKWebView component (look for import WebKit or references to WKWebView in the application's codebase).
    Affected if The application uses WKWebView and the underlying OS is running a version listed in step 1.
  3. For third-party app developers, check the SDK version used for building
    Inspect the Xcode project settings or build logs to determine which iOS/macOS SDK version was used to compile the application.
    Affected if The app was built with an SDK version prior to iOS 16.1, iPadOS 16.0, macOS 13.0, tvOS 16.1, or watchOS 9.1.
  4. Verify enterprise mobile device management (MDM) enrolled devices
    Query the MDM console or use management APIs to list all enrolled iOS, iPadOS, macOS, tvOS, or watchOS devices and their current OS versions.
    Affected if Any managed devices are running OS versions below the fixed releases listed above and have applications using WKWebView.

The environment is affected if any device runs an OS version below the fixed releases (iOS 16.1+, iPadOS 16+, macOS 13+, tvOS 16.1+, watchOS 9.1+) AND uses applications that leverage WKWebView for rendering 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.1 / 13.0 / 16.0 or later
Fixed in 9.113.016.0
Interim mitigation

Apply the vendor-supplied security updates (iOS 16.1+, iPadOS 16+, macOS Ventura 13+, tvOS 16.1+, watchOS 9.1+) to all affected devices. For third-party applications using WKWebView, ensure applications are rebuilt against updated SDKs and deployed to endpoint devices.

Recommended fix High confidence

iPadOS 16+, iOS 16.1+, macOS Ventura 13+, tvOS 16.1+, watchOS 9.1+

  1. Upgrade iPadOS to version 16.0 or later (iPadOS 16.1 recommended)
  2. Upgrade iPhone iOS to version 16.1 or later
  3. Upgrade macOS to version 13.0 (Ventura) or later
  4. Upgrade tvOS to version 16.1 or later
  5. Upgrade watchOS to version 9.1 or later
  6. After upgrading, verify the WKWebView component is updated by checking system settings or running: sw_vers on macOS, or checking Settings > General > Software Update on iOS devices
Caveat Major OS upgrades may introduce compatibility issues with older applications or configurations; backup data before upgrading

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

Fix this in Ipados Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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