Heap corruption via Presentation API use-after-free
Published May 30, 2024 · Updated Feb 13, 2025
Use-after-free in Google Chrome's Presentation API before 125.0.6422.141 allows remote attackers to exploit heap corruption. Public advisories identify the affected component but do not disclose the freed object's lifetime error or the operation that reuses it. A user must open a crafted HTML page; successful exploitation can compromise the browser process, subject to Chrome's sandbox.
Summary
What happened
Use-after-free in Google Chrome's Presentation API before 125.0.6422.141 allows remote attackers to exploit heap corruption. Public advisories identify the affected component but do not disclose the freed object's lifetime error or the operation that reuses it. A user must open a crafted HTML page; successful exploitation can compromise the browser process, subject to Chrome's sandbox.
The record
- CVE
- CVE-2024-5498
- Published
- May 30, 2024
- Updated
- Feb 13, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, 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=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.
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