Heap corruption via Browser UI bounds error
Published May 30, 2024 · Updated Feb 13, 2025
Out-of-bounds memory access in Google Chrome before 125.0.6422.141 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies the Browser UI as the affected component but has not disclosed the operation or input whose bounds are mishandled. Exploitation requires a user to open the page and perform specific UI gestures, after which heap corruption can compromise the browser process.
Summary
What happened
Out-of-bounds memory access in Google Chrome before 125.0.6422.141 allows remote attackers to corrupt heap memory via crafted HTML. Google identifies the Browser UI as the affected component but has not disclosed the operation or input whose bounds are mishandled. Exploitation requires a user to open the page and perform specific UI gestures, after which heap corruption can compromise the browser process.
The record
- CVE
- CVE-2024-5497
- Published
- May 30, 2024
- Updated
- Feb 13, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, CWE-125, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 30, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record 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 <125.0.6422.141
- Affected versionversion=125.0.6422.141 <125.0.6422.141
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
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