dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 13 Feb 2024.
SafariWeb browser · Apple

CVE-2024-23222

HIGH · 8.8 CVSS v3.1 Published 2024-01-23
Fix available
A fix is available. Upgrade to 1.0.2 / 12.7.3 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild 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 type confusion issue was addressed with improved checks. This issue is fixed in Safari 17.3, iOS 15.8.7 and iPadOS 15.8.7, iOS 16.7.5 and iPadOS 16.7.5, iOS 17.3 and iPadOS 17.3, macOS Monterey 12.7.3, macOS Sonoma 14.3, macOS Ventura 13.6.4, tvOS 17.3, visionOS 1.0.2. Processing maliciously crafted web content may lead to arbitrary code execution. This fix associated with the Coruna exploit was shipped in iOS 17.3 on January 22, 2024. This update brings that fix to devices that cannot update to the latest iOS version.

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

This is a type confusion vulnerability in WebKit (Apple's browser rendering engine) that allows arbitrary code execution when processing maliciously crafted web content. The issue was addressed with improved type checking in the affected Safari and iOS/macOS versions. It is associated with the 'Coruna' exploit chain.

MitigationApply vendor-provided patches by updating to Safari 17.3, iOS/iPadOS 17.3 or 16.7.5/15.8.7, macOS Sonoma 14.3/Ventura 13.6.4/Monterey 12.7.3, tvOS 17.3, or visionOS 1.0.2 as appropriate for each affected device.

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:< 17.3
IpadosOperating system
Affected:< 15.8.7>= 16.0, < 16.7.5>= 17.0, < 17.3
Iphone OsOperating system
Affected:< 15.8.7>= 16.0, < 16.7.5>= 17.0, < 17.3
macOSOperating system
Affected:>= 12.0, < 12.7.3>= 13.0, < 13.6.4>= 14.0, < 14.3
TvosOperating system
Affected:< 17.3
VisionosOperating system
Affected:< 1.0.2

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 menu > About Safari. The version number appears next to 'Safari'. Compare to the affected versions: < 12.7.3 for Monterey, < 13.6.4 for Ventura, < 14.3 for Sonoma, or < 17.3 generally.
    Affected if The displayed Safari version falls below 17.3 (or below the version threshold for your specific macOS release as listed in the affected products)
  2. Check macOS system version
    Click Apple menu > About This Mac. The version number is displayed (e.g., 12.7.2, 13.6.3, 14.2.1). Compare against the affected ranges: < 12.7.3, >= 13.0 and < 13.6.4, >= 14.0 and < 14.3.
    Affected if The macOS version falls within any of the affected ranges and you use Safari or any WebKit-based browser.
  3. Check iOS or iPadOS version on iPhone/iPad
    Go to Settings > General > About. The version shown (e.g., 16.7.4, 17.2) is the iOS version. Compare against affected ranges: < 15.8.7, >= 16.0 and < 16.7.5, >= 17.0 and < 17.3.
    Affected if The iOS/iPadOS version is within any affected range and you use Safari or any WebKit-based browser (all iOS browsers rely on WebKit).
  4. Check tvOS version on Apple TV
    Go to Settings > General > About > Version. Compare the tvOS version against the affected range: < 17.3.
    Affected if The tvOS version is below 17.3 and you use the Safari or browsing app on Apple TV.
  5. Check visionOS version on Apple Vision Pro
    Go to Settings > General > About. The version is displayed. Compare against affected range: < 1.0.2.
    Affected if The visionOS version is below 1.0.2 and you use Safari or any browser in the visionOS environment.

You are affected if your device runs any Safari, iOS, iPadOS, macOS, tvOS, or visionOS version within the affected ranges AND you process web content through a WebKit-based browser or application.

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 1.0.2 / 12.7.3 / 13.6.4 or later
Fixed in 1.0.212.7.313.6.4
Interim mitigation

Apply vendor-provided patches by updating to Safari 17.3, iOS/iPadOS 17.3 or 16.7.5/15.8.7, macOS Sonoma 14.3/Ventura 13.6.4/Monterey 12.7.3, tvOS 17.3, or visionOS 1.0.2 as appropriate for each affected device.

Recommended fix High confidence

Update to Safari 17.3, iOS/iPadOS 15.8.7/16.7.5/17.3, macOS Monterey 12.7.3/Ventura 13.6.4/Sonoma 14.3, tvOS 17.3, or visionOS 1.0.2 as applicable to your device

  1. Identify the current version of the affected Apple product (Safari, iOS, iPadOS, macOS, tvOS, or visionOS)
  2. For iPhone/iPad: Go to Settings > General > Software Update and install the appropriate update: iOS 17.3/iPadOS 17.3, iOS 16.7.5/iPadOS 16.7.5, or iOS 15.8.7/iPadOS 15.8.7
  3. For macOS: Open System Settings > General > Software Update and install: macOS Sonoma 14.3, macOS Ventura 13.6.4, or macOS Monterey 12.7.3
  4. For Safari: Update via macOS update (Safari 17.3 is included in macOS Sonoma 14.3)
  5. For tvOS: Go to Settings > General > Privacy & Security > Software Update and install tvOS 17.3
  6. For visionOS: Go to Settings > General > Software Update and install visionOS 1.0.2
  7. After updating, verify the version number matches the fixed release for your device
Caveat Standard OS update; ensure backup of important data before updating; some older devices may not support the latest OS versions

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

Fix this in Safari Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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