Process crash via malformed WebKit content
Published Dec 11, 2024 · Updated May 28, 2026
Memory corruption in WebKit on affected Apple platforms allows remote attackers to crash a web-content process via crafted content. Apple has not disclosed the affected WebKit routine or the memory-lifetime or bounds operation that mishandles attacker-controlled web content. Opening or rendering the content is required; the reported consequence is an unexpected process crash, not a device reboot or data compromise.
Summary
What happened
Memory corruption in WebKit on affected Apple platforms allows remote attackers to crash a web-content process via crafted content. Apple has not disclosed the affected WebKit routine or the memory-lifetime or bounds operation that mishandles attacker-controlled web content. Opening or rendering the content is required; the reported consequence is an unexpected process crash, not a device reboot or data compromise.
The record
- CVE
- CVE-2024-54508
- Published
- Dec 11, 2024
- Updated
- May 28, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-125, CWE-787, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 11, 2024CVE publishedPublication date reported by the CVE source.
- May 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <18.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo