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.
CPE | Name | Operator | Version |
---|---|---|---|
ubuntu_linux | eq | 16.04 | |
ubuntu_linux | eq | 15.10 | |
ubuntu_linux | eq | 14.04 | |
debian_linux | eq | 8.0 | |
chrome | le | 50.0.2661.102 | |
v8 | le | 5.0.71 | |
leap | eq | 42.1 | |
opensuse | eq | 13.2 | |
enterprise_linux_desktop | eq | 6.0 | |
enterprise_linux_server | eq | 6.0 |
lists.opensuse.org/opensuse-security-announce/2016-05/msg00062.html
lists.opensuse.org/opensuse-security-announce/2016-05/msg00063.html
lists.opensuse.org/opensuse-security-announce/2016-06/msg00005.html
www.debian.org/security/2016/dsa-3590
www.securityfocus.com/bid/90876
www.securitytracker.com/id/1035981
www.ubuntu.com/usn/USN-2992-1
access.redhat.com/errata/RHSA-2016:1190
codereview.chromium.org/1875053002
crbug.com/595259
googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html
security.gentoo.org/glsa/201607-07