CVE-2017-15406: Buffer Overflow
First published: Thu Oct 26 2017(Updated: )
A stack buffer overflow in V8 in Google Chrome prior to 62.0.3202.75 allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page.
Credit: cve-coordination@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Chrome (Trace Event) | <62.0.3202.75 | 62.0.3202.75 |
| Google Chrome (Trace Event) | <62.0.3202.75 |
Remedy
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-2017-15406?
CVE-2017-15406 is classified as a high severity vulnerability due to its potential for exploitation through crafted HTML pages.
How do I fix CVE-2017-15406?
To fix CVE-2017-15406, update your Google Chrome browser to version 62.0.3202.75 or later.
What type of vulnerability is CVE-2017-15406?
CVE-2017-15406 is a stack buffer overflow vulnerability in the V8 engine of Google Chrome.
What could an attacker achieve by exploiting CVE-2017-15406?
An attacker could perform an out of bounds memory read, potentially compromising the integrity of the user's system.
Which software versions are affected by CVE-2017-15406?
CVE-2017-15406 affects Google Chrome versions prior to 62.0.3202.75.
- agent/references
- agent/type
- agent/last-modified-date
- agent/softwarecombine
- agent/first-publish-date
- agent/event
- agent/author
- agent/severity
- agent/remedy
- agent/weakness
- agent/description
- agent/tags
- collector/chrome-releases
- agent/software-canonical-lookup-request
- agent/software-canonical-lookup
- collector/nvd-index
- vendor/google
- canonical/google chrome (trace event)