Heap corruption via crafted PDF processing
Published Sep 23, 2024 · Updated Sep 24, 2024
Heap buffer overflow in Google Chrome's PDF component before 124.0.6367.78 allows remote attackers to corrupt heap memory with a crafted PDF file. Google has not published the affected PDF-processing routine or the incorrect bounds operation that permits the heap overwrite. Rendering an attacker-supplied PDF is required; the public record does not identify the resulting post-corruption capability.
Summary
What happened
Heap buffer overflow in Google Chrome's PDF component before 124.0.6367.78 allows remote attackers to corrupt heap memory with a crafted PDF file. Google has not published the affected PDF-processing routine or the incorrect bounds operation that permits the heap overwrite. Rendering an attacker-supplied PDF is required; the public record does not identify the resulting post-corruption capability.
The record
- CVE
- CVE-2024-7018
- Published
- Sep 23, 2024
- Updated
- Sep 24, 2024
- Vendor
- Google Cloud
- Product
- Google Chrome
- Classifications
- CWE-122, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 23, 2024CVE publishedPublication date reported by the CVE source.
- Sep 24, 2024Record 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=0 <124.0.6367.78
- Affected versionversion=124.0.6367.78 <124.0.6367.78
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