dbcve.org
SafariWeb browser · Apple

CVE-2024-27820

HIGH · 8.8 CVSS v3.1 Published 2024-06-10
Fix available
A fix is available. Upgrade to 1.2 / 10.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
The issue was addressed with improved memory handling. This issue is fixed in Safari 17.5, iOS 16.7.8 and iPadOS 16.7.8, iOS 17.5 and iPadOS 17.5, macOS Sonoma 14.5, tvOS 17.5, visionOS 1.2, watchOS 10.5. 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 · high confidence

A memory handling vulnerability in WebKit allows arbitrary code execution when processing malicious web content. This affects Safari and multiple Apple operating systems (iOS, iPadOS, macOS, tvOS, visionOS, watchOS). The fix involves improved memory handling in the patched versions.

MitigationUpdate all affected devices to the fixed versions: Safari 17.5, iOS/iPadOS 16.7.8 or 17.5, macOS Sonoma 14.5, tvOS 17.5, visionOS 1.2, or watchOS 10.5.

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.5
IpadosOperating system
Affected:< 16.7.8>= 17.0, < 17.5
Iphone OsOperating system
Affected:< 16.7.8>= 17.0, < 17.5
macOSOperating system
Affected:>= 14.0, < 14.5
TvosOperating system
Affected:< 17.5
VisionosOperating system
Affected:< 1.2
WatchosOperating system
Affected:< 10.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. Identify the Apple product
    Determine which Apple device and operating system is in use (iPhone, iPad, Mac, Apple TV, Apple Watch, Apple Vision Pro)
    Affected if The device runs any of the affected Apple operating systems listed in the CVE
  2. Check Safari version on iOS/iPadOS
    Go to Settings > Safari > About to view the Safari version. Compare to affected versions: < 16.7.8 or >= 17.0 and < 17.5
    Affected if Safari version is lower than 16.7.8, or is 17.0 through 17.4.x on iOS/iPadOS
  3. Check Safari version on macOS
    Open Safari, go to Safari > About Safari to view the version. Compare to affected versions: < 17.5
    Affected if Safari version is 17.4.x or earlier on macOS
  4. Check macOS version
    Go to System Settings > About to view the macOS version. Compare to affected versions: 14.0 through 14.4.x (Sonoma)
    Affected if macOS Sonoma version is 14.0 through 14.4.x, regardless of Safari version
  5. Check tvOS, watchOS, or visionOS version
    On Apple TV: Settings > General > About > Version. On Apple Watch: Settings > General > About > Watch OS. On Apple Vision Pro: Settings > General > About > visionOS. Compare to affected versions: tvOS < 17.5, watchOS < 10.5, visionOS < 1.2
    Affected if tvOS is earlier than 17.5, watchOS is earlier than 10.5, or visionOS is earlier than 1.2

You are affected if any Apple device in your environment runs Safari or an app that uses WebKit with a version lower than the fixed versions (Safari 17.5, iOS/iPadOS 16.7.8 or 17.5, macOS 14.5, tvOS 17.5, visionOS 1.2, watchOS 10.5).

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.2 / 10.5 / 14.5 or later
Fixed in 1.210.514.5
Interim mitigation

Update all affected devices to the fixed versions: Safari 17.5, iOS/iPadOS 16.7.8 or 17.5, macOS Sonoma 14.5, tvOS 17.5, visionOS 1.2, or watchOS 10.5.

Recommended fix High confidence

Safari 17.5, iOS/iPadOS 16.7.8 or 17.5, macOS Sonoma 14.5, tvOS 17.5, visionOS 1.2, watchOS 10.5

  1. 1. Identify the Apple device (iPhone, iPad, Mac, Apple Watch, Apple TV, or Apple Vision Pro) and current operating system version
  2. 2. For iPhone/iPad: Go to Settings > General > Software Update and install iOS/iPadOS 17.5 (or iOS/iPadOS 16.7.8 for devices on the 16.x branch)
  3. 3. For Mac: Go to System Settings > General > Software Update and install macOS Sonoma 14.5
  4. 4. For Apple Watch: Open the Watch app on iPhone, go to My Watch > General > Software Update and install watchOS 10.5
  5. 5. For Apple TV: Go to Settings > System > Software Updates and install tvOS 17.5
  6. 6. For Apple Vision Pro: Go to Settings > General > Software Updates and install visionOS 1.2
  7. 7. For Safari: Update to Safari 17.5 (included with macOS 14.5, or standalone for earlier macOS versions)
  8. 8. After updating, verify the fix by processing web content in Safari - the vulnerability should no longer be exploitable
Caveat Apple security updates typically have minimal breaking changes; ensure backups before updating

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

Fix this in Safari Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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