Heap corruption via Layout integer overflow
Published Nov 27, 2024 · Updated Nov 27, 2024
Integer overflow in Google Chrome Layout before 129.0.6668.89 allows remote attackers to corrupt heap memory via crafted HTML. The Blink ruby-text justification path computes a string-view length from impl.length() minus offset without first validating the subtraction. Exploitation requires a user to open the page; the published testcase reaches a fatal assertion and crashes the renderer, while Google reports broader heap corruption.
Summary
What happened
Integer overflow in Google Chrome Layout before 129.0.6668.89 allows remote attackers to corrupt heap memory via crafted HTML. The Blink ruby-text justification path computes a string-view length from impl.length() minus offset without first validating the subtraction. Exploitation requires a user to open the page; the published testcase reaches a fatal assertion and crashes the renderer, while Google reports broader heap corruption.
The record
- CVE
- CVE-2024-7025
- Published
- Nov 27, 2024
- Updated
- Nov 27, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-190, CWE-472, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 27, 2024CVE publishedPublication date reported by the CVE source.
- Nov 27, 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.89
- Affected versionversion=129.0.6668.89 <129.0.6668.89
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.
Weakness, pattern, technique
Public exploit references
- Crafted ruby-text layout testcaseproof of concept · demonstrated
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