Heap corruption via crafted HTML page
Published Aug 6, 2024 · Updated Oct 24, 2024
Inappropriate implementation in V8 in Google Chrome before 127.0.6533.99 allows remote attackers to trigger heap corruption via crafted HTML. Google has not disclosed the V8 code path or the incorrect operation that permits the crafted page to corrupt heap memory. The attack requires a user to open attacker-controlled content, and the published record does not define the post-corruption consequence.
Summary
What happened
Inappropriate implementation in V8 in Google Chrome before 127.0.6533.99 allows remote attackers to trigger heap corruption via crafted HTML. Google has not disclosed the V8 code path or the incorrect operation that permits the crafted page to corrupt heap memory. The attack requires a user to open attacker-controlled content, and the published record does not define the post-corruption consequence.
The record
- CVE
- CVE-2024-7535
- Published
- Aug 6, 2024
- Updated
- Oct 24, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 6, 2024CVE publishedPublication date reported by the CVE source.
- Oct 24, 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 <127.0.6533.99
- Affected versionversion=127.0.6533.99 <127.0.6533.99
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