Upstream information
Description
Google V8, as used in Google Chrome before 34.0.1847.116, does not properly implement lazy deoptimization, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via crafted JavaScript code, as demonstrated by improper handling of a heap allocation of a number outside the Small Integer (aka smi) range.SUSE information
Overall state of this security issue: Does not affect SUSE products
This issue is currently rated as having important severity.
| CVSS detail | National Vulnerability Database |
|---|---|
| Base Score | 7.5 |
| Vector | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| Access Vector | Network |
| Access Complexity | Low |
| Authentication | None |
| Confidentiality Impact | Partial |
| Integrity Impact | Partial |
| Availability Impact | Partial |
SUSE Security Advisories:
- openSUSE-SU-2014:0601-1
List of released packages
| Product(s) | Fixed package version(s) | References |
|---|---|---|
| openSUSE Leap 15.0 |
| Patchnames: openSUSE Leap 15.0 GA chromium-66.0.3359.170-lp150.1.1 |
| openSUSE Tumbleweed |
| Patchnames: openSUSE-Tumbleweed-2024-10171 openSUSE-Tumbleweed-2024-12948 |
SUSE Timeline for this CVE
CVE page created: Wed Apr 9 14:17:40 2014CVE page last modified: Mon Oct 6 18:20:35 2025