Heap corruption via use-after-free in UI
Published Oct 15, 2024 · Updated Oct 16, 2024
Use-after-free in the UI of Google Chrome on iOS before 130.0.6723.58 allows remote attackers to trigger heap corruption through crafted HTML. The UI accesses an object after it has been freed; Google has not disclosed the object, function, or exact event sequence. Exploitation requires a user to load the page and perform specific UI gestures; successful exploitation corrupts heap memory in the browser process.
Summary
What happened
Use-after-free in the UI of Google Chrome on iOS before 130.0.6723.58 allows remote attackers to trigger heap corruption through crafted HTML. The UI accesses an object after it has been freed; Google has not disclosed the object, function, or exact event sequence. Exploitation requires a user to load the page and perform specific UI gestures; successful exploitation corrupts heap memory in the browser process.
The record
- CVE
- CVE-2024-9957
- Published
- Oct 15, 2024
- Updated
- Oct 16, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 15, 2024CVE publishedPublication date reported by the CVE source.
- Oct 16, 2024Record 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 <130.0.6723.58
- Affected versionversion=130.0.6723.58 <130.0.6723.58
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