Description
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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
n/a n/a
n/aaffected
References
- http://www.securityfocus.com/bid/90876 ↗
- https://crbug.com/595259 ↗
- https://codereview.chromium.org/1875053002 ↗
- http://lists.opensuse.org/opensuse-security-announce/2016-06/msg00005.html ↗
- http://www.securitytracker.com/id/1035981 ↗
- http://www.debian.org/security/2016/dsa-3590 ↗
- http://googlechromereleases.blogspot.com/2016/05/stable-channel-update_25.html ↗
- http://www.ubuntu.com/usn/USN-2992-1 ↗
- http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00062.html ↗
- https://access.redhat.com/errata/RHSA-2016:1190 ↗
- https://security.gentoo.org/glsa/201607-07 ↗
- http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00063.html ↗