CVE-2024-54502
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 · uneditedThe issue was addressed with improved checks. 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 confidenceThis is a denial-of-service vulnerability in Safari and Apple device OS components where processing maliciously crafted web content triggers an unexpected process crash. The fix implemented improved checks (likely input validation or bounds checking) to prevent the crash condition.
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< 18.2< 18.2< 18.2>= 15.0, < 15.2< 18.2< 2.2< 11.2CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Check Safari version on macOS or iOSOn macOS, open Safari and select Safari > About Safari. On iOS/iPadOS, go to Settings > Safari > About. Note the version number displayed.Affected if The version is earlier than 18.2 (e.g., 18.1.x, 18.0.x, or any 17.x version)
-
Check iOS or iPadOS versionGo to Settings > General > About > Version on the device. Note the OS version number.Affected if The version is earlier than 18.2 (for example, 18.1, 17.x) - note that 17.7.6 is also patched so check if below 17.7.6 if staying on iOS 17 branch
-
Check macOS versionClick the Apple menu > About This Mac. Note the macOS version (such as 15.1, 15.0).Affected if The macOS version is 15.0 or 15.1 (versions 15.0 through 15.1.x are vulnerable, fixed in 15.2)
-
Check tvOS versionOpen Settings > General > About > Version on the Apple TV device.Affected if The version is earlier than 18.2 (such as 18.1, 18.0, or earlier)
-
Check visionOS versionOpen Settings > General > About > Version on the Apple Vision Pro device.Affected if The version is earlier than 2.2 (such as 2.1, 2.0, or earlier)
-
Check watchOS versionOn Apple Watch: go to Settings > General > About. Or on paired iPhone: open Watch app > My Watch > General > About. Note the watchOS version.Affected if The version is earlier than 11.2 (such as 11.1, 11.0, or earlier)
You are affected if any Safari, iOS, iPadOS, macOS, tvOS, visionOS, or watchOS device in your environment runs a version lower than the fixed releases (Safari 18.2, iOS/iPadOS 18.2 or 17.7.6, macOS 15.2, tvOS 18.2, visionOS 2.2, watchOS 11.2).
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.211.215.2
Apply the available vendor patches: upgrade 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.
Upgrade to Safari 18.2, iOS 18.2, iPadOS 18.2 (or 17.7.6 for older iPads), macOS Sequoia 15.2, tvOS 18.2, visionOS 2.2, or watchOS 11.2 depending on device
- For iPhone and iPad: Go to Settings > General > Software Update and install iOS 18.2 or iPadOS 18.2
- For Mac: Go to System Settings > General > Software Update and install macOS Sequoia 15.2
- For Safari (standalone on macOS): Update to Safari 18.2 via Mac App Store or system update
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 18.2
- For Apple Watch: On your iPhone, open the Watch app, go to General > Software Update and install watchOS 11.2
- For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 2.2
- For older iPadOS 17 devices: Install iPadOS 17.7.6 via Settings > General > Software Update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54502 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-54502 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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