dbcve.org
SafariWeb browser · Apple

CVE-2022-42799

MEDIUM · 6.1 CVSS v3.1 Published 2022-11-01
Fix available
A fix is available. Upgrade to 9.1 / 13.0 or later.
See remediation →
68/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
The issue was addressed with improved UI handling. This issue is fixed in tvOS 16.1, macOS Ventura 13, watchOS 9.1, Safari 16.1, iOS 16.1 and iPadOS 16. Visiting a malicious website may lead to user interface spoofing.

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 UI spoofing vulnerability in Safari and WebKit across multiple Apple platforms allows malicious websites to manipulate the browser's user interface, potentially tricking users into believing they are viewing legitimate content. The vulnerability stems from improper UI handling in the browser rendering engine.

MitigationApply the vendor-supplied updates: iOS 16.1/iPadOS 16 or later, macOS Ventura 13 or later, watchOS 9.1 or later, tvOS 16.1 or later, and Safari 16.1 or later.

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.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 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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Check Safari version on macOS
    Open Safari, click Safari menu > About Safari. Compare the version number shown to the affected range (versions before 16.1).
    Affected if The displayed version is lower than 16.1
  2. Check iOS version for Safari on iPhone/iPad
    Go to Settings > General > About. Look for the iOS version number. Note that Safari on iOS uses the WebKit engine, and iOS versions before 16.0 are affected.
    Affected if iOS or iPadOS version is lower than 16.0
  3. Check macOS version for built-in WebKit
    Go to Apple menu > About This Mac. The macOS version determines the bundled WebKit and Safari versions. macOS versions before 13.0 include vulnerable WebKit.
    Affected if macOS version is lower than 13.0 (Ventura)
  4. Check watchOS version on Apple Watch
    Open the Watch app on iPhone, go to General > About, or check on Apple Watch via Settings > General > About. Versions before 9.1 are affected.
    Affected if watchOS version is lower than 9.1
  5. Check tvOS version on Apple TV
    Go to Settings > General > About Apple TV. Versions before 16.1 include vulnerable WebKit.
    Affected if tvOS version is lower than 16.1

If any of the browser or OS versions listed above are below the minimum fixed versions (Safari 16.1, iOS/iPadOS 16.0, macOS 13.0, watchOS 9.1, tvOS 16.1), the environment is vulnerable to UI spoofing attacks when visiting malicious websites.

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 updates: iOS 16.1/iPadOS 16 or later, macOS Ventura 13 or later, watchOS 9.1 or later, tvOS 16.1 or later, and Safari 16.1 or later.

Recommended fix High confidence

Apple: iOS 16.1+, iPadOS 16+, macOS 13+ (Ventura), watchOS 9.1+, tvOS 16.1+, Safari 16.1+ | Linux: Apply vendor security updates via package manager

  1. For Apple devices: Update to the fixed version via Settings > General > Software Update (iOS/iPadOS), System Preferences > Software Update (macOS), or the Watch/TV apps for watchOS and tvOS.
  2. For Safari on macOS: Update Safari by installing macOS Ventura 13, Monterey 12.5.7, or Big Sur 11.7.7 as appropriate for your Mac model.
  3. For Fedora Linux: Run 'sudo dnf update webkit2gtk' or 'sudo dnf update' to apply security patches.
  4. For Debian Linux: Run 'sudo apt update && sudo apt upgrade' to apply available security updates for the webkit2gtk package.
Caveat Standard OS update considerations apply - ensure backups and check app compatibility 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-42799 — 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-42799 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