Heap corruption via PDF object use-after-free
Published Sep 26, 2022 · Updated May 21, 2025
Use-after-free in Google Chrome's PDF component before 105.0.5195.125 allows remote attackers to trigger heap corruption via a crafted PDF file. The component references memory after releasing it while parsing attacker-controlled PDF content; Google has not disclosed the affected function or object type. A user must open or render the file; the documented consequence is heap corruption, while Google has not stated whether exploitation yields code execution or a deterministic crash.
Summary
What happened
Use-after-free in Google Chrome's PDF component before 105.0.5195.125 allows remote attackers to trigger heap corruption via a crafted PDF file. The component references memory after releasing it while parsing attacker-controlled PDF content; Google has not disclosed the affected function or object type. A user must open or render the file; the documented consequence is heap corruption, while Google has not stated whether exploitation yields code execution or a deterministic crash.
The record
- CVE
- CVE-2022-3197
- Published
- Sep 26, 2022
- Updated
- May 21, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-416, T1204.002, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 26, 2022CVE publishedPublication date reported by the CVE source.
- May 21, 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=unspecified <105.0.5195.125
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