Heap corruption via crafted PDF interaction
Published Oct 11, 2023 · Updated May 1, 2025
Heap buffer overflow in Chrome's PDF component before 118.0.5993.70 allows remote attackers to trigger heap corruption through a crafted PDF. Google has not disclosed the affected code locus or exact bounds error; the linked issue remains access-restricted. Reaching the overflow requires specific user interaction with the PDF, and the public record establishes no reliable outcome beyond heap corruption.
Summary
What happened
Heap buffer overflow in Chrome's PDF component before 118.0.5993.70 allows remote attackers to trigger heap corruption through a crafted PDF. Google has not disclosed the affected code locus or exact bounds error; the linked issue remains access-restricted. Reaching the overflow requires specific user interaction with the PDF, and the public record establishes no reliable outcome beyond heap corruption.
The record
- CVE
- CVE-2023-5474
- Published
- Oct 11, 2023
- Updated
- May 1, 2025
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 11, 2023CVE publishedPublication date reported by the CVE source.
- May 1, 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=118.0.5993.70 <118.0.5993.70
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