CVE-2014-1721
N/A
Published: April 9, 2014 at 10:00 AM UTC
Updated: June 17, 2026 at 12:05 AM UTC
1 product affected across 1 vendorChrome
Using N/A by N/A?
Get instant alerts when new vulnerabilities affect N/A - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 2%
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.
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
References (6)
x_refsource_CONFIRM
Source: [email protected]
http://googlechromereleases.blogspot.com/2014/04/stable-channel-update.htmlVendor Advisoryx_refsource_SUSE
Source: [email protected]
http://lists.opensuse.org/opensuse-updates/2014-05/msg00012.htmlVendor Advisoryx_refsource_GENTOO
Source: [email protected]
http://security.gentoo.org/glsa/glsa-201408-16.xmlVendor Advisoryx_refsource_DEBIAN
Source: [email protected]
http://www.debian.org/security/2014/dsa-2905x_refsource_CONFIRM
Source: [email protected]
https://code.google.com/p/chromium/issues/detail?id=350434Quick Info
StatusMODIFIED
CWE
CWE-189
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card