Memory corruption via WebKit out-of-bounds write
Published Jan 27, 2025 · Updated Apr 2, 2026
An out-of-bounds write in WebKit on affected Apple platforms allows remote attackers to corrupt memory via crafted web content. Apple links the flaw to WebKit Bugzilla 282450 but has not published the affected function or the unchecked write operation. Successful triggering requires the target to process attacker-controlled web content; the published consequence is memory corruption.
Summary
What happened
An out-of-bounds write in WebKit on affected Apple platforms allows remote attackers to corrupt memory via crafted web content. Apple links the flaw to WebKit Bugzilla 282450 but has not published the affected function or the unchecked write operation. Successful triggering requires the target to process attacker-controlled web content; the published consequence is memory corruption.
The record
- CVE
- CVE-2024-54543
- Published
- Jan 27, 2025
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 27, 2025CVE publishedPublication date reported by the CVE source.
- Apr 2, 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.
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