CVE-2024-54551
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 memory handling. This issue is fixed in Safari 17.6, iOS 17.6 and iPadOS 17.6, macOS Sonoma 14.6, tvOS 17.6, visionOS 1.3, watchOS 10.6. Processing web content may lead to a denial-of-service.
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 confidenceA memory handling vulnerability in WebKit allows processing malicious web content to cause a denial-of-service condition. This affects Safari and WebKit-based browsers across multiple Apple platforms including iOS, iPadOS, macOS, tvOS, visionOS, and watchOS.
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< 17.6< 17.6< 17.6< 14.6< 17.6< 1.3< 10.6CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Safari or WebKit browser version on the deviceOn macOS: Open Safari, go to Safari menu > About Safari. On iOS/iPadOS: Go to Settings > Safari > About. On tvOS: Go to Settings > Apps > Safari > About. On visionOS: Go to Settings > Safari > About. On watchOS: Open the Watch app on paired iPhone, go to Safari > About.Affected if The displayed version number is lower than 17.6 for Safari, iOS, iPadOS, tvOS; lower than 14.6 for macOS; lower than 1.3 for visionOS; or lower than 10.6 for watchOS.
-
Confirm the operating system version matches the affected platformOn macOS: Apple menu > About This Mac. On iOS/iPadOS: Settings > General > About. On tvOS: Settings > General > About. On visionOS: Settings > General > About. On watchOS: Watch app on iPhone > My Watch > About.Affected if The OS version is below 17.6 for iOS/iPadOS/tvOS, below 14.6 for macOS Sonoma, below 1.3 for visionOS, or below 10.6 for watchOS, and the browser version is also below the corresponding threshold.
-
Check if Safari or any WebKit-based browser is actively usedReview installed browsers on the device. Common WebKit-based browsers include Safari, Chrome (on iOS uses WebKit), Firefox (on iOS uses WebKit), and third-party browsers on iOS that rely on WebKit.Affected if Safari or any WebKit-based browser is installed and was used to process untrusted web content.
-
Verify whether the device received the latest available updateOn iOS/iPadOS: Settings > General > Software Update. On macOS: System Settings > General > Software Update. On tvOS: Settings > General > Software Update. On visionOS: Settings > General > Software Update. On watchOS: On the watch: Settings > General > Software Update, or via Watch app on iPhone.Affected if The device shows an available update to a version at or above the fixed releases (iOS/iPadOS 17.6, macOS 14.6, tvOS 17.6, visionOS 1.3, watchOS 10.6).
A user is affected if Safari or a WebKit-based browser is running on an Apple platform with a version lower than the fixed releases (Safari 17.6, iOS/iPadOS 17.6, macOS 14.6, tvOS 17.6, visionOS 1.3, watchOS 10.6) and the browser has been used to access untrusted web content.
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 · scoped1.310.614.6
Update all affected Apple devices to the patched versions: Safari 17.6, iOS/iPadOS 17.6, macOS Sonoma 14.6, tvOS 17.6, visionOS 1.3, or watchOS 10.6 and later.
iOS 17.6, iPadOS 17.6, macOS Sonoma 14.6, tvOS 17.6, visionOS 1.3, watchOS 10.6, Safari 17.6
- For iPhone/iPad: Go to Settings > General > Software Update and install iOS/iPadOS 17.6 or later
- For Mac: Open System Settings > General > Software Update and install macOS Sonoma 14.6 or later
- For Apple Watch: Open the Watch app on iPhone > General > Software Update and install watchOS 10.6 or later
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 17.6 or later
- For Vision Pro: Go to Settings > General > Software Update and install visionOS 1.3 or later
- For Safari standalone: Update macOS to 14.6 which includes Safari 17.6
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54551 — 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-54551 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