SafariWeb browser · Apple

CVE-2024-54508

HIGH · 7.5 CVSS v3.1 Published 2024-12-12
Fix available
A fix is available. Upgrade to 2.2 / 11.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 18.2, iOS 18.2 and iPadOS 18.2, iPadOS 17.7.6, macOS Sequoia 15.2, tvOS 18.2, visionOS 2.2, watchOS 11.2. Processing maliciously crafted web content may lead to an unexpected process crash.

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

CVE-2024-54508 is a memory handling vulnerability in multiple Apple platforms (Safari, iOS, iPadOS, macOS, tvOS, visionOS, watchOS) that allows remote code execution or denial of service via maliciously crafted web content, resulting in an unexpected process crash.

MitigationApply the vendor-supplied patches by updating to Safari 18.2, iOS/iPadOS 18.2 or 17.7.6, macOS Sequoia 15.2, tvOS 18.2, visionOS 2.2, or watchOS 11.2 as appropriate for each affected system.

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:< 18.2
IpadosOperating system
Affected:< 18.2
Iphone OsOperating system
Affected:< 18.2
macOSOperating system
Affected:< 15.2
TvosOperating system
Affected:< 18.2
VisionosOperating system
Affected:< 2.2
WatchosOperating system
Affected:< 11.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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 is lower than 18.2
  2. Check iOS or iPadOS version
    Go to Settings > General > About on iPhone or iPad; the version number is shown next to 'Software Version'
    Affected if Version is lower than 18.2 (or not 17.7.6)
  3. Check macOS version
    Click Apple menu > About This Mac; the macOS version is shown below the operating system name
    Affected if Version is lower than 15.2 (Sequoia)
  4. Check tvOS, visionOS, or watchOS version
    On the device, go to Settings > General > About to view the tvOS, visionOS, or watchOS version
    Affected if tvOS is lower than 18.2, visionOS is lower than 2.2, or watchOS is lower than 11.2
  5. Confirm web content exposure
    Verify that Safari or any webkit-based browser is used to access the internet
    Affected if Web browsing is enabled and any of the above version conditions are true

You are affected if you run any Safari version below 18.2 or any affected Apple OS version below the patched release (macOS 15.2, iOS/iPadOS 18.2 or 17.7.6, tvOS 18.2, visionOS 2.2, watchOS 11.2) and use web browsing functionality.

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 2.2 / 11.2 / 15.2 or later
Fixed in 2.211.215.2
Interim mitigation

Apply the vendor-supplied patches by updating to Safari 18.2, iOS/iPadOS 18.2 or 17.7.6, macOS Sequoia 15.2, tvOS 18.2, visionOS 2.2, or watchOS 11.2 as appropriate for each affected system.

Recommended fix High confidence

Upgrade to Safari 18.2, iOS/iPadOS 18.2 (or iPadOS 17.7.6 for older devices), macOS Sequoia 15.2, tvOS 18.2, visionOS 2.2, or watchOS 11.2 depending on device type

  1. Identify the affected Apple device(s) in your environment and current OS version
  2. For iPhone/iPad: Go to Settings > General > Software Update and upgrade to iOS 18.2 / iPadOS 18.2, or for older supported devices upgrade to iPadOS 17.7.6
  3. For Mac: Go to System Settings > General > Software Update and upgrade to macOS Sequoia 15.2
  4. For Apple Watch: Open the Watch app on iPhone, go to General > Software Update and upgrade to watchOS 11.2
  5. For Apple TV: Go to Settings > System > Software Updates and upgrade to tvOS 18.2
  6. For Apple Vision Pro: Go to Settings > General > Software Update and upgrade to visionOS 2.2
  7. For Safari standalone: Upgrade via the respective OS update to Safari 18.2
  8. After updating, verify the Safari version is 18.2 or later via Safari > About Safari
Caveat Standard OS upgrade considerations apply - review app compatibility and backup data before upgrading

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

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-54508 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-54508 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