First published: Thu May 26 2016(Updated: )
objects.cc in Google V8 before 5.0.71.32, as used in Google Chrome before 51.0.2704.63, does not properly restrict lazy deoptimization, which allows remote attackers to cause a denial of service (heap-based buffer overflow) or possibly have unspecified other impact via crafted JavaScript code.
Credit: cve-coordination@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/Chrome | <51.0.2704.63 | 51.0.2704.63 |
Google V8 | <=5.0.71 | |
Google Chrome | <=50.0.2661.102 | |
Ubuntu | =14.04 | |
Ubuntu | =15.10 | |
Ubuntu | =16.04 | |
Debian | =8.0 | |
openSUSE | =42.1 | |
openSUSE | =13.2 | |
redhat enterprise Linux desktop | =6.0 | |
redhat enterprise Linux server | =6.0 | |
redhat enterprise Linux workstation | =6.0 | |
SUSE Linux Enterprise Server | =12.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-1678 is classified as a moderate severity vulnerability due to its potential for denial of service attacks.
To fix CVE-2016-1678, update Google Chrome to version 51.0.2704.63 or later.
CVE-2016-1678 can lead to a heap-based buffer overflow, resulting in potential denial of service.
CVE-2016-1678 affects Google V8 versions up to 5.0.71 and Google Chrome versions up to 50.0.2661.102.
Yes, a patch is available in the form of the updated Google Chrome version 51.0.2704.63.