CVE-2024-54478
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 · uneditedAn out-of-bounds access issue was addressed with improved bounds checking. This issue is fixed in iOS 18.2 and iPadOS 18.2, iPadOS 17.7.4, macOS Sequoia 15.2, macOS Sonoma 14.7.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 · high confidenceThis is an out-of-bounds memory access vulnerability in WebKit (Apple's browser engine) that allows processing of maliciously crafted web content to cause an unexpected process crash. The fix involves improved bounds checking in the affected components.
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.7.4>= 18.0, < 18.2< 18.2< 14.7.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.
-
Identify your Apple device typeDetermine whether the device is an iPhone, iPad, Mac, Apple TV, Vision Pro, or Apple Watch. This is needed because version ranges differ by platform.Affected if The device runs any of the affected Apple operating systems listed in the CVE.
-
Check iOS or iPadOS versionOn iPhone or iPad, go to Settings > General > About and read the Version number. For iPad, the same path applies in iPadOS.Affected if The version is less than 17.7.4, or is 18.0 through 18.1.x (18.0 <= version < 18.2).
-
Check macOS versionOn Mac, go to System Settings > General > About (or System Preferences > About on older macOS) and read the Version number.Affected if The version is less than 14.7.2, or is 15.0 through 15.1.x (15.0 <= version < 15.2).
-
Check tvOS versionOn Apple TV, go to Settings > General > About and read the Version number.Affected if The version is less than 18.2.
-
Check watchOS versionOn Apple Watch, go to Settings > General > About and read the Version number, or check via the paired iPhone in the Watch app.Affected if The version is 11.2 or lower (version <= 11.2).
-
Check visionOS versionOn Apple Vision Pro, go to Settings > General > About and read the Version number.Affected if The version is less than 2.2.
If your device runs an Apple OS version that falls within any of the affected ranges (iOS < 17.7.4 or 18.0-18.1.x, macOS < 14.7.2 or 15.0-15.1.x, tvOS < 18.2, watchOS <= 11.2, visionOS < 2.2), then your environment is affected by this WebKit vulnerability.
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.214.7.215.2
Apply the vendor-supplied patches by updating all affected Apple devices to iOS 18.2/iPadOS 18.2/17.7.4, macOS Sequoia 15.2/Sonoma 14.7.2, tvOS 18.2, visionOS 2.2, or watchOS 11.2 as appropriate.
iOS 18.2, iPadOS 18.2, iPadOS 17.7.4, macOS Sonoma 14.7.2, macOS Sequoia 15.2, tvOS 18.2, visionOS 2.2, watchOS 11.2
- Open Settings app on iPhone or iPad
- Go to General > Software Update
- Download and install iOS 18.2 or iPadOS 18.2 (or iPadOS 17.7.4 for older devices)
- For Mac: open System Settings > General > Software Update and install macOS Sonoma 14.7.2 or macOS Sequoia 15.2
- For Apple TV: go to Settings > System > Software Updates and install tvOS 18.2
- For Apple Watch: open the Watch app on iPhone, go to My Watch > General > Software Update and install watchOS 11.2
- For Vision Pro: go to Settings > General > Software Update and install visionOS 2.2
- Restart the device after the update completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54478 — 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-54478 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