dbcve.org
SafariWeb browser · Apple

CVE-2024-23213

HIGH · 8.8 CVSS v3.1 Published 2024-01-23
Fix available
A fix is available. Upgrade to 10.3 / 14.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
The issue was addressed with improved memory handling. This issue is fixed in Safari 17.3, iOS 16.7.5 and iPadOS 16.7.5, iOS 17.3 and iPadOS 17.3, macOS Sonoma 14.3, tvOS 17.3, watchOS 10.3. Processing 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

A memory handling vulnerability in WebKit allows arbitrary code execution when processing malicious web content. The issue stems from improper memory management, likely a use-after-free or similar memory corruption flaw that can be triggered by visiting a crafted webpage.

MitigationUpdate affected Apple devices to Safari 17.3, iOS/iPadOS 16.7.5 or 17.3, macOS Sonoma 14.3, tvOS 17.3, or watchOS 10.3. Organizations should enforce software updates across managed Apple device fleets.

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:> 16.0, < 16.7.5> 17.0, < 17.3
Iphone OsOperating system
Affected:> 16.0, < 16.7.5> 17.0, < 17.3
macOSOperating system
Affected:>= 14.0, < 14.3
TvosOperating system
Affected:< 17.3
WatchosOperating system
Affected:< 10.3

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 or iOS/iPadOS
    Open Safari and navigate to Safari > About Safari (macOS) or Settings > Safari > About (iOS/iPadOS). Note the version number displayed.
    Affected if Version is below 17.3 (e.g., 17.2.x, 17.1.x, 16.x) on any platform running Safari.
  2. Check macOS version
    Click the Apple menu > System Settings > General > About. Note the macOS version (e.g., 14.2, 14.1, 13.x).
    Affected if macOS version is 14.0, 14.1, or 14.2 (falls within >= 14.0, < 14.3).
  3. Check iOS or iPadOS version
    Open Settings > General > About on the iPhone or iPad. Note the iOS version number.
    Affected if iOS/iPadOS version is 16.7.4 or earlier, or any version 17.0 to 17.2.x (ranges >16.0 to <16.7.5 or >17.0 to <17.3).
  4. Check tvOS version
    Open Settings > General > About on Apple TV. Note the tvOS version number.
    Affected if tvOS version is any version below 17.3 (e.g., 17.2.x, 17.1.x, 16.x).
  5. Check watchOS version
    Open the Watch app on paired iPhone, go to My Watch > General > About. Note the watchOS version number.
    Affected if watchOS version is any version below 10.3 (e.g., 10.2.x, 10.1.x, 9.x).

You are affected if any Apple device runs Safari below 17.3, macOS 14.0-14.2, iOS/iPadOS 16.7.4 or 17.0-17.2.x, tvOS below 17.3, or watchOS below 10.3.

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 10.3 / 14.3 / 16.7.5 or later
Fixed in 10.314.316.7.5
Interim mitigation

Update affected Apple devices to Safari 17.3, iOS/iPadOS 16.7.5 or 17.3, macOS Sonoma 14.3, tvOS 17.3, or watchOS 10.3. Organizations should enforce software updates across managed Apple device fleets.

Recommended fix High confidence

Safari 17.3, iOS 16.7.5/17.3, iPadOS 16.7.5/17.3, macOS Sonoma 14.3, tvOS 17.3, or watchOS 10.3 (depending on device)

  1. Identify the affected Apple device and current OS/browser version
  2. For iPhone/iPad: Go to Settings > General > Software Update and update to iOS/iPadOS 16.7.5 or 17.3 depending on your target version
  3. For Mac: Go to System Settings > Software Update and update to macOS Sonoma 14.3
  4. For Safari on older macOS: Update to Safari 17.3 via Mac App Store or Software Update
  5. For Apple TV: Go to Settings > System > Software Updates and update to tvOS 17.3
  6. For Apple Watch: On iPhone, open Watch app, go to My Watch > General > Software Update and update to watchOS 10.3
  7. After updating, verify the new version in Settings/About
Caveat Standard OS update risks apply - review Apple release notes for any known issues before updating critical devices

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

Fix this in Safari Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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