dbcve.org
SafariWeb browser · Apple

CVE-2024-54505

HIGH · 8.8 CVSS v3.1 Published 2024-12-12
Fix available
A fix is available. Upgrade to 2.2 / 11.2 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 type confusion 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.3, macOS Sequoia 15.2, tvOS 18.2, visionOS 2.2, watchOS 11.2. Processing maliciously crafted web content may lead to memory corruption.

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 type confusion vulnerability in WebKit allows remote attackers to cause memory corruption by tricking users into visiting malicious websites. The issue stems from improper memory handling during web content processing, potentially allowing arbitrary code execution.

MitigationUpdate to the fixed versions (Safari 18.2, iOS/iPadOS 18.2 or 17.7.3, macOS Sequoia 15.2, tvOS 18.2, visionOS 2.2, watchOS 11.2) or avoid visiting untrusted websites.

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:< 17.7.3>= 18.0, < 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
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. Note the version number displayed.
    Affected if Version is earlier than 18.2 (e.g., 18.1.x or older)
  2. Check iOS version on iPhone
    Go to Settings > General > About. Note the version number next to 'Software Version'.
    Affected if Version is earlier than 17.7.3, OR is 18.0 or 18.1.x (i.e., less than 18.2 but not 17.7.3)
  3. Check iPadOS version on iPad
    Go to Settings > General > About. Note the version number next to 'Software Version'.
    Affected if Version is earlier than 17.7.3, OR is 18.0 or 18.1.x (i.e., less than 18.2 but not 17.7.3)
  4. Check macOS version
    Click Apple menu > About This Mac. Note the macOS version (e.g., Sequoia 15.x, Sonoma 14.x, etc.).
    Affected if macOS version is earlier than 15.2 (e.g., 15.1.x or older, or any earlier macOS release)
  5. Check tvOS version on Apple TV
    Go to Settings > General > About > Version. Note the tvOS version number.
    Affected if Version is earlier than 18.2

You are affected if any Apple device you use runs software versions lower than the fixed releases (Safari 18.2, iOS/iPadOS 18.2 or 17.7.3, macOS 15.2, tvOS 18.2, visionOS 2.2, watchOS 11.2) and you use WebKit-based browsers or visit websites.

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

Update to the fixed versions (Safari 18.2, iOS/iPadOS 18.2 or 17.7.3, macOS Sequoia 15.2, tvOS 18.2, visionOS 2.2, watchOS 11.2) or avoid visiting untrusted websites.

Recommended fix High confidence

Safari 18.2, iOS 18.2, iPadOS 18.2/17.7.3, macOS Sequoia 15.2, tvOS 18.2, visionOS 2.2, watchOS 11.2

  1. Update Safari to version 18.2 or later
  2. Update iOS devices to version 18.2 or later
  3. Update iPadOS devices to version 18.2 (or 17.7.3 for iPadOS 17.x devices)
  4. Update macOS to version 15.2 (Sequoia) or later
  5. Update tvOS devices to version 18.2 or later
  6. Update visionOS devices to version 2.2 or later
  7. Update watchOS devices to version 11.2 or later
  8. Ensure automatic updates are enabled for future security patches
Caveat Standard Apple security update with minimal risk; some legacy web content may render differently

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

Fix this in Safari Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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