Heap corruption via PDF integer overflow
Published Feb 22, 2023 · Updated May 5, 2025
Integer overflow in the PDF component of Google Chrome before 110.0.5481.177 allows remote attackers to corrupt heap memory via a crafted PDF file. Google identifies the faulty operation only as an integer overflow in PDF; the underlying parser locus and arithmetic operation remain restricted. Successful exploitation requires user interaction with the crafted PDF and yields heap corruption inside the browser process.
Summary
What happened
Integer overflow in the PDF component of Google Chrome before 110.0.5481.177 allows remote attackers to corrupt heap memory via a crafted PDF file. Google identifies the faulty operation only as an integer overflow in PDF; the underlying parser locus and arithmetic operation remain restricted. Successful exploitation requires user interaction with the crafted PDF and yields heap corruption inside the browser process.
The record
- CVE
- CVE-2023-0933
- Published
- Feb 22, 2023
- Updated
- May 5, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-190, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 22, 2023CVE publishedPublication date reported by the CVE source.
- May 5, 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=110.0.5481.177 <110.0.5481.177
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