CVE-2018-20066: Use After Free
First published: Wed Jan 09 2019(Updated: )
Incorrect object lifecycle in Extensions in Google Chrome prior to 71.0.3578.80 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Credit: cve-coordination@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Chrome | <71.0.3578.80 |
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-2018-20066?
CVE-2018-20066 has a medium severity rating due to its potential for exploitation through heap corruption.
How do I fix CVE-2018-20066?
To fix CVE-2018-20066, upgrade Google Chrome to version 71.0.3578.80 or later.
What versions of Google Chrome are affected by CVE-2018-20066?
CVE-2018-20066 affects Google Chrome versions prior to 71.0.3578.80.
Who can exploit CVE-2018-20066?
A remote attacker could exploit CVE-2018-20066 by using a crafted HTML page to cause heap corruption.
What type of attack does CVE-2018-20066 involve?
CVE-2018-20066 involves a potential heap corruption attack through vulnerabilities in the object lifecycle of extensions.
- agent/references
- agent/type
- agent/softwarecombine
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/severity
- agent/author
- agent/weakness
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/trending
- agent/tags
- agent/source
- vendor/google
- canonical/google chrome