dbcve.org
SafariWeb browser · Apple

CVE-2022-22610

HIGH · 8.8 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to 8.5 / 12.3 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
A memory corruption issue was addressed with improved state management. This issue is fixed in macOS Monterey 12.3, Safari 15.4, watchOS 8.5, iOS 15.4 and iPadOS 15.4, tvOS 15.4. Processing maliciously crafted web content may lead to 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

Memory corruption vulnerability in WebKit affecting Safari and iOS Safari. Triggered by maliciously crafted web content, it allows remote code execution via state management errors in memory handling.

MitigationApply vendor patches: macOS Monterey 12.3+, Safari 15.4+, iOS/iPadOS 15.4+, watchOS 8.5+, tvOS 15.4+. Prioritize patching browser-facing systems.

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:< 15.4
Ipad OsOperating system
Affected:< 15.4
Iphone OsOperating system
Affected:< 15.4
macOSOperating system
Affected:>= 12.0, < 12.3
TvosOperating system
Affected:< 15.4
WatchosOperating system
Affected:< 8.5

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, go to Safari > About Safari, or run: defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString
    Affected if Version is earlier than 15.4
  2. Check macOS Monterey version
    Open System Settings > General > About, or run: sw_vers -productVersion
    Affected if Version is 12.0 or higher but lower than 12.3
  3. Check iOS version on iPhone
    Go to Settings > General > About, note the Version number
    Affected if Version is earlier than 15.4
  4. Check iPadOS version on iPad
    Go to Settings > General > About, note the Version number
    Affected if Version is earlier than 15.4
  5. Check tvOS version on Apple TV
    Go to Settings > General > About TV, note the Version number
    Affected if Version is earlier than 15.4
  6. Check watchOS version on Apple Watch
    On paired iPhone, open Watch app > General > About, note the Version; or go to Settings > General > About on the watch itself
    Affected if Version is earlier than 8.5

You are affected if any Apple device or browser listed above is running an unpatched version within the vulnerable ranges specified.

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.5 / 12.3 / 15.4 or later
Fixed in 8.512.315.4
Interim mitigation

Apply vendor patches: macOS Monterey 12.3+, Safari 15.4+, iOS/iPadOS 15.4+, watchOS 8.5+, tvOS 15.4+. Prioritize patching browser-facing systems.

Recommended fix High confidence

Upgrade to iOS 15.4 / iPadOS 15.4 / watchOS 8.5 / tvOS 15.4 / macOS Monterey 12.3 / Safari 15.4 depending on device

  1. For iPhone and iPad: Go to Settings > General > Software Update and install iOS/iPadOS 15.4 or later
  2. For Apple Watch: On iPhone, open the Watch app, go to My Watch > General > Software Update and install watchOS 8.5 or later
  3. For Apple TV: Go to Settings > System > Software Updates and install tvOS 15.4 or later
  4. For macOS: Go to System Preferences > Software Update and install macOS Monterey 12.3 or later
  5. For Safari on older macOS: If Safari 15.4 is available for your macOS version, update via System Preferences > Software Update
Caveat Major OS upgrades may introduce app compatibility changes; backup data before updating

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

Fix this in Safari Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
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,488.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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