dbcve.org
IpadosOperating system · Apple

CVE-2022-32792

HIGH · 8.8 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to 8.7 / 12.5 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
An out-of-bounds write issue was addressed with improved input validation. This issue is fixed in iOS 15.6 and iPadOS 15.6, watchOS 8.7, tvOS 15.6, macOS Monterey 12.5, Safari 15.6. 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 · moderate confidence

An out-of-bounds write vulnerability in WebKit (Apple's browser engine) allows processing of maliciously crafted web content to trigger memory corruption, potentially leading to arbitrary code execution. The issue stems from insufficient input validation in web content processing.

MitigationApply the vendor-supplied security updates: iOS 15.6+, iPadOS 15.6+, watchOS 8.7+, tvOS 15.6+, macOS Monterey 12.5+, and Safari 15.6+. For enterprise environments, deploy these updates via MDM or patch management infrastructure.

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:< 15.6
Iphone OsOperating system
Affected:< 15.6
macOSOperating system
Affected:>= 12.0, < 12.5
TvosOperating system
Affected:< 15.6
WatchosOperating system
Affected:< 8.7

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 your Apple device and operating system
    Determine whether the system is an iPhone, iPad, Mac, Apple TV, or Apple Watch, and note which operating system it runs (iOS, iPadOS, macOS, tvOS, or watchOS).
    Affected if The device runs any of the affected Apple operating systems.
  2. Check the installed iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About to view the version number. Compare it to the affected range: versions before 15.6 are vulnerable.
    Affected if The installed iOS or iPadOS version is earlier than 15.6.
  3. Check the installed macOS version
    On Mac, click the Apple menu > About This Mac to view the macOS version. Compare it to the affected range: versions 12.0 through 12.4 are vulnerable.
    Affected if The installed macOS version is 12.0, 12.1, 12.2, 12.3, or 12.4.
  4. Check the installed tvOS or watchOS version
    On Apple TV, go to Settings > General > About > Version. On Apple Watch, open the Watch app on iPhone > General > About. Compare to the affected ranges: tvOS and watchOS versions before 15.6 and 8.7 respectively are vulnerable.
    Affected if The installed tvOS version is earlier than 15.6 or watchOS version is earlier than 8.7.
  5. Verify WebKit-based browser usage
    Confirm that Safari or any third-party browser using the WebKit engine is in use, as this vulnerability is triggered when processing web content through WebKit.
    Affected if WebKit-based browsers are used on an affected operating system version.

You are affected if your device runs iOS, iPadOS, tvOS, or watchOS before 15.6 (or 8.7 for watchOS), or macOS Monterey between 12.0 and 12.4, and you use WebKit-based browsers.

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 8.7 / 12.5 / 15.6 or later
Fixed in 8.712.515.6
Interim mitigation

Apply the vendor-supplied security updates: iOS 15.6+, iPadOS 15.6+, watchOS 8.7+, tvOS 15.6+, macOS Monterey 12.5+, and Safari 15.6+. For enterprise environments, deploy these updates via MDM or patch management infrastructure.

Recommended fix High confidence

iOS 15.6, iPadOS 15.6, watchOS 8.7, tvOS 15.6, macOS Monterey 12.5

  1. Back up your device data before updating
  2. Update iOS devices to version 15.6 or later via Settings > General > Software Update
  3. Update iPadOS devices to version 15.6 or later via Settings > General > Software Update
  4. Update watchOS devices to version 8.7 or later via the Watch app on iPhone or directly on the Apple Watch
  5. Update tvOS devices to version 15.6 or later via Settings > General > Apple TV Software Update
  6. Update macOS devices to version 12.5 (Monterey) or later via System Preferences > Software Update
  7. After updating, verify the installed version matches or exceeds the fixed release
Caveat Standard OS update risks apply; minor OS updates typically have minimal breaking changes but always backup before updating

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

Fix this in Ipados Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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