CVE-2024-7018: Buffer Overflow
First published: Mon Sep 23 2024(Updated: )
Heap buffer overflow in PDF in Google Chrome prior to 124.0.6367.78 allowed a remote attacker to potentially exploit heap corruption via a crafted PDF file. (Chromium security severity: Medium)
Credit: chrome-cve-admin@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Chrome (Trace Event) | <124.0.6367.78 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-7018?
The severity of CVE-2024-7018 is classified as Medium.
How do I fix CVE-2024-7018?
To fix CVE-2024-7018, update Google Chrome to version 124.0.6367.78 or later.
What does CVE-2024-7018 impact?
CVE-2024-7018 impacts Google Chrome versions prior to 124.0.6367.78.
Can CVE-2024-7018 be exploited remotely?
Yes, CVE-2024-7018 can potentially be exploited remotely via a crafted PDF file.
What type of vulnerability is CVE-2024-7018?
CVE-2024-7018 is a heap buffer overflow vulnerability.
- agent/references
- agent/type
- agent/description
- agent/first-publish-date
- agent/author
- agent/event
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/weakness
- agent/softwarecombine
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/google
- canonical/google chrome (trace event)