dbcve.org
SafariWeb browser · Apple

CVE-2022-32912

HIGH · 8.8 CVSS v3.1 Published 2022-09-20
Fix available
A fix is available. Upgrade to 15.7 / 16.0 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 read was addressed with improved bounds checking. This issue is fixed in Safari 16, iOS 16, iOS 15.7 and iPadOS 15.7. 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

CVE-2022-32912 is an out-of-bounds read vulnerability in WebKit (Apple's browser engine) affecting Safari 16 and iOS/iPadOS 15.x. The vulnerability stems from insufficient bounds checking when processing maliciously crafted web content, allowing an attacker to read memory beyond allocated buffers. Successful exploitation can lead to arbitrary code execution with the privileges of the rendering process.

MitigationApply the vendor-supplied updates: Safari 16, iOS 16, iOS 15.7, or iPadOS 15.7 or later. Organizations should inventory all affected devices and ensure automatic updates are enabled or deploy patches via MDM.

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.0
IpadosOperating system
Affected:< 15.7
Iphone OsOperating system
Affected:< 15.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. Check Safari version on macOS
    Open Safari, click Safari menu > About Safari, or run 'defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString' in Terminal
    Affected if Version displayed is less than 16.0 (e.g., 15.x)
  2. Check iOS version on iPhone
    Open Settings > General > About on the device and note the version number next to 'Version'
    Affected if Version is less than 15.7 (e.g., 15.6.x or earlier)
  3. Check iPadOS version on iPad
    Open Settings > General > About on the iPad and note the version number next to 'Version'
    Affected if Version is less than 15.7 (e.g., 15.6.x or earlier)
  4. Confirm WebKit-based browsers on the system
    Identify any third-party browsers using WebKit (such as Chrome on iOS) which also contain the same WebKit engine and are thus affected by this vulnerability
    Affected if Any WebKit-based browser is present on an affected iOS/iPadOS version

You are affected if Safari is below 16.0 on macOS, or iOS/iPadOS is below 15.7 on mobile devices, as the vulnerable WebKit component is present in these unpatched versions.

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 15.7 / 16.0 or later
Fixed in 15.716.0
Interim mitigation

Apply the vendor-supplied updates: Safari 16, iOS 16, iOS 15.7, or iPadOS 15.7 or later. Organizations should inventory all affected devices and ensure automatic updates are enabled or deploy patches via MDM.

Recommended fix High confidence

Safari 16, iOS 16, iOS 15.7, iPadOS 15.7

  1. Identify the current version of Safari, iOS, or iPadOS on the affected device
  2. For iPhone: Go to Settings > General > Software Update to check for and install iOS 16 or iOS 15.7
  3. For iPad: Go to Settings > General > Software Update to check for and install iPadOS 15.7
  4. For Mac: Open App Store > Updates to check for and install Safari 16
  5. Ensure the device is connected to Wi-Fi and has sufficient battery before updating
  6. After updating, verify the new version by checking Settings > General > About

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