SafariWeb browser · Apple

CVE-2022-42823

HIGH · 8.8 CVSS v3.1 Published 2022-11-01

Fix available

A fix is available. Upgrade to 9.1 / 13.0 or later.

See remediation →

95/100

Remediation priority · Urgent

Remotely reachable No privileges

Official description

NVD · unedited

A type confusion issue was addressed with improved memory handling. This issue is fixed in tvOS 16.1, macOS Ventura 13, watchOS 9.1, Safari 16.1, iOS 16.1 and iPadOS 16. Processing maliciously crafted web content may lead to arbitrary code execution.

Technical summary

dbcve analysis · high confidence

A type confusion vulnerability in WebKit (Safari's rendering engine) allows arbitrary code execution when processing maliciously crafted web content. The issue was addressed with improved memory handling in Safari 16.1, iOS/iPadOS 16.1, tvOS 16.1, watchOS 9.1, and macOS Ventura 13.

MitigationApply the available Apple security updates (iOS 16.1+, iPadOS 16.1+, macOS Ventura 13+, Safari 16.1+, tvOS 16.1+, watchOS 9.1+) to all affected devices. Prioritize devices with web browser exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

SafariWeb browser

Affected:< 16.1

FedoraOperating system

Affected:= 35= 36= 37

Debian LinuxOperating system

Affected:= 10.0= 11.0

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

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check Safari version on macOS

Open Safari, go to Safari > About Safari to view the version number. Compare it to the affected range (versions before 16.1 are vulnerable).

Affected if Safari version is lower than 16.1 and the browser is used to process untrusted web content
Check iOS or iPadOS version on Apple mobile devices

Go to Settings > General > About to view the iOS/iPadOS version. Compare against affected ranges (iOS < 16.1, iPadOS < 16.0).

Affected if iOS version is lower than 16.1 or iPadOS version is lower than 16.0 and Safari is used
Check macOS version

Go to Apple menu > About This Mac to view the macOS version. Compare against the affected range (versions before 13.0 Ventura).

Affected if macOS version is lower than 13.0 and Safari or other WebKit-based browsers are used
Check tvOS or watchOS version on Apple TV or Apple Watch

On Apple TV: go to Settings > General > About. On Apple Watch: go to Settings > General > About. Compare against affected ranges (tvOS < 16.1, watchOS < 9.1).

Affected if tvOS version is lower than 16.1 or watchOS version is lower than 9.1 and the built-in browser is used
Identify WebKit-based browsers on Linux systems

On Fedora: run 'rpm -qa | grep webkit'. On Debian: run 'dpkg -l | grep webkit' to list installed WebKit packages.

Affected if WebKit packages are installed from affected Fedora (35, 36, 37) or Debian (10.0, 11.0) releases and browsers using WebKit are run

A user is affected if they run any Apple product (Safari, iOS, iPadOS, macOS, tvOS, watchOS) or Linux distribution with WebKit below the patched versions specified in the affected ranges and process web content with those browsers.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 9.1 / 13.0 / 16.0 or later

Fixed in 9.113.016.0

Interim mitigation

Apply the available Apple security updates (iOS 16.1+, iPadOS 16.1+, macOS Ventura 13+, Safari 16.1+, tvOS 16.1+, watchOS 9.1+) to all affected devices. Prioritize devices with web browser exposure.

Recommended fix High confidence

iOS 16.1, iPadOS 16.1, macOS Ventura 13, watchOS 9.1, tvOS 16.1, Safari 16.1; Linux distros should update WebKit packages to latest available

For iOS devices: Go to Settings > General > Software Update and install iOS 16.1 or later
For iPadOS devices: Go to Settings > General > Software Update and install iPadOS 16.1 or later
For macOS devices: Go to System Preferences > Software Update and install macOS Ventura 13 or later
For watchOS devices: On iPhone, open Watch app > General > Software Update and install watchOS 9.1 or later
For tvOS devices: Go to Settings > System > Software Updates and install tvOS 16.1 or later
For Safari: Update via macOS Ventura 13 or install Safari 16.1 via Software Update on supported macOS versions
For Linux distributions (Fedora/Debian): Update system packages via 'dnf update' or 'apt update && apt upgrade' to receive WebKit security patches

Caveat Major OS version upgrades (e.g., to macOS Ventura 13) may introduce compatibility issues with older applications; always backup before upgrading

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-42823 — 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

Primary sources

support.apple.comVendor Advisory
support.apple.comVendor Advisory
support.apple.comVendor Advisory
support.apple.comVendor Advisory
support.apple.comVendor Advisory
www.openwall.comMailing ListThird Party Advisory
lists.debian.orgMailing ListThird Party Advisory
www.debian.orgThird Party Advisory
www.debian.orgThird Party Advisory
lists.fedoraproject.org
lists.fedoraproject.org
lists.fedoraproject.org
security.gentoo.org
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-42823 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2022-42823?

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.

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

At a glance

A fix existsUpgrade to 9.1 / 13.0 or later

Severity 8.8 High

Exploit likelihood EPSS, next 30 days 1.5%

Affects: Safari

Remediation

A high-priority fix

Fix this in Safari 14 hrs · Moderate

Typical engagement from $2,490

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2022-42823 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References