Heap corruption via Serial use-after-free
Published Nov 6, 2024 · Updated Nov 6, 2024
Use-after-free in Serial in Google Chrome before 130.0.6723.116 allows remote attackers to trigger heap corruption via crafted HTML. Google has not published the faulty function or object-lifetime operation; the referenced issue remains restricted to authorized viewers. A user must load attacker-controlled HTML, and the public record does not establish a specific post-corruption outcome.
Summary
What happened
Use-after-free in Serial in Google Chrome before 130.0.6723.116 allows remote attackers to trigger heap corruption via crafted HTML. Google has not published the faulty function or object-lifetime operation; the referenced issue remains restricted to authorized viewers. A user must load attacker-controlled HTML, and the public record does not establish a specific post-corruption outcome.
The record
- CVE
- CVE-2024-10827
- Published
- Nov 6, 2024
- Updated
- Nov 6, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 6, 2024CVE publishedPublication date reported by the CVE source.
- Nov 6, 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.116
- Affected versionversion=130.0.6723.116 <130.0.6723.116
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