Stack corruption via crafted HTML page
Published Sep 17, 2024 · Updated Sep 18, 2024
Memory corruption in V8 in Google Cloud Google Chrome before 129.0.6668.58 allows remote attackers to corrupt the stack via crafted HTML. Google has not published the flawed V8 operation that mishandles the page content, and the referenced issue remains access-restricted. Exploitation requires a user to open attacker-controlled HTML; public sources do not establish a post-corruption capability.
Summary
What happened
Memory corruption in V8 in Google Cloud Google Chrome before 129.0.6668.58 allows remote attackers to corrupt the stack via crafted HTML. Google has not published the flawed V8 operation that mishandles the page content, and the referenced issue remains access-restricted. Exploitation requires a user to open attacker-controlled HTML; public sources do not establish a post-corruption capability.
The record
- CVE
- CVE-2024-8905
- Published
- Sep 17, 2024
- Updated
- Sep 18, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2024CVE publishedPublication date reported by the CVE source.
- Sep 18, 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 <129.0.6668.58
- Affected versionversion=129.0.6668.58 <129.0.6668.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