Heap corruption via DevTools use-after-free
Published Jan 29, 2025 · Updated Jan 29, 2025
Use-after-free in Google Chrome DevTools before 132.0.6834.159 allows remote attackers to corrupt heap memory via a crafted Chrome extension. Chrome identifies DevTools as the affected component but has not disclosed which object is freed prematurely or later dereferenced. User interaction with the crafted extension is required; successful exploitation compromises confidentiality, integrity, and availability in the browser's security context.
Summary
What happened
Use-after-free in Google Chrome DevTools before 132.0.6834.159 allows remote attackers to corrupt heap memory via a crafted Chrome extension. Chrome identifies DevTools as the affected component but has not disclosed which object is freed prematurely or later dereferenced. User interaction with the crafted extension is required; successful exploitation compromises confidentiality, integrity, and availability in the browser's security context.
The record
- CVE
- CVE-2025-0762
- Published
- Jan 29, 2025
- Updated
- Jan 29, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 29, 2025CVE publishedPublication date reported by the CVE source.
- Jan 29, 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.159 <132.0.6834.159
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.
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