Stack corruption via crafted Tracing input
Published Jan 15, 2025 · Updated Mar 20, 2025
Stack buffer overflow in Google Chrome's Tracing component before 132.0.6834.83 allows remote attackers to corrupt memory via crafted HTML. Google has not published the affected Tracing routine or the unchecked operation that overflows its stack buffer. The attack requires a user to load the page and yields memory corruption within the browser process; further code-level consequences are undisclosed.
Summary
What happened
Stack buffer overflow in Google Chrome's Tracing component before 132.0.6834.83 allows remote attackers to corrupt memory via crafted HTML. Google has not published the affected Tracing routine or the unchecked operation that overflows its stack buffer. The attack requires a user to load the page and yields memory corruption within the browser process; further code-level consequences are undisclosed.
The record
- CVE
- CVE-2025-0438
- Published
- Jan 15, 2025
- Updated
- Mar 20, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-121, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 15, 2025CVE publishedPublication date reported by the CVE source.
- Mar 20, 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=132.0.6834.83 <132.0.6834.83
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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