CVE-2016-1679: Use After Free

Published May 26, 2016
·
Updated

A heap use-after-free flaw was found in the V8 bindings component of the Chromium browser.

Upstream bug(s):

https://code.google.com/p/chromium/issues/detail?id=606390

External References:

http://googlechromereleases.blogspot.com/2016/05/stable-channel-update25.html

Other sources

The ToV8Value function in content/child/v8valueconverterimpl.cc in the V8 bindings in Google Chrome before 51.0.2704.63 does not properly restrict use of getters and setters, which allows remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via crafted JavaScript code.

MITRE

Affected Software

12 affected componentsFixes available
redhat/Chrome<51.0.2704.63
51.0.2704.63
Google Chrome<=50.0.2661.102
Canonical Ubuntu Linux=14.04
Canonical Ubuntu Linux=15.10
Canonical Ubuntu Linux=16.04
Debian Debian Linux=8.0
openSUSE Leap=42.1
openSUSE openSUSE=13.2
redhat Enterprise Linux Desktop=6.0
redhat Enterprise Linux Server=6.0
redhat Enterprise Linux Workstation=6.0
SUSE Linux Enterprise=12.0

Event History

Jun 5, 2016
CVE Published
via MITRE·11:00 PM
Data Sourced
via MITRE·11:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2016-1679?

CVE-2016-1679 has been rated as a moderate severity vulnerability due to its potential to cause a denial of service and unspecified impacts.

2

How do I fix CVE-2016-1679?

To fix CVE-2016-1679, update Google Chrome to version 51.0.2704.63 or later.

3

What software is affected by CVE-2016-1679?

CVE-2016-1679 affects multiple versions of Google Chrome prior to version 51.0.2704.63.

4

Can CVE-2016-1679 lead to remote code execution?

CVE-2016-1679 does not directly indicate remote code execution, but it can cause a denial of service which may lead to other vulnerabilities being exploited.

5

Is there a workaround for CVE-2016-1679?

There is no known workaround for CVE-2016-1679, making it essential to apply the update to mitigate the vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203