CVE-2014-1721
published 2014-04-09CVE-2014-1721: 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…
PriorityP430high7.5CVSS 2.0
AVNACLAuNCPIPAP
EPSS
1.57%
72.9th percentile
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.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| chrome | <= 34.0.1847.115 | — |
CVSS provenance
nvdv2.07.5HIGHAV:N/AC:L/Au:N/C:P/I:P/A:P
osv7.5HIGH
vendor_redhat7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-fqrm-g3fv-x64c: Google V8, as used in Google Chrome before 34
ghsa_unreviewed·2022-05-17
CVE-2014-1721 [HIGH] GHSA-fqrm-g3fv-x64c: Google V8, as used in Google Chrome before 34
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.
OSV
CVE-2014-1721: Google V8, as used in Google Chrome before 34
osv·2014-04-09·CVSS 7.5
CVE-2014-1721 [HIGH] CVE-2014-1721: Google V8, as used in Google Chrome before 34
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.
Red Hat
v8: memory corruption issue fixed in Google Chrome 34.0.1847.116
vendor_redhat·2014-03-12·CVSS 7.5
CVE-2014-1721 [HIGH] v8: memory corruption issue fixed in Google Chrome 34.0.1847.116
v8: memory corruption issue fixed in Google Chrome 34.0.1847.116
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.
Package: ruby193-v8 (CloudForms Management Engine 5) - Not affected
Package: ruby193-v8 (OpenShift Enterprise 1) - Not affected
Package: v8 (Red Hat OpenShift Enterprise 2) - Not affected
Package: ruby193-v8 (Red Hat OpenStack Platform 3) - Not affected
Package: v8 (Red Hat OpenStack Platform 3) - Not affected
Package: ruby193-v8 (Red Hat OpenStack Platfor
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2014-1721 v8: memory corruption issue fixed in Google Chrome 34.0.1847.116
bugzilla·2014-04-10·CVSS 7.5
CVE-2014-1721 [HIGH] CVE-2014-1721 v8: memory corruption issue fixed in Google Chrome 34.0.1847.116
CVE-2014-1721 v8: memory corruption issue fixed in Google Chrome 34.0.1847.116
Common Vulnerabilities and Exposures assigned an identifier CVE-2014-1721 to
the following vulnerability:
Name: CVE-2014-1721
URL: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-1721
Assigned: 20140129
Reference: http://googlechromereleases.blogspot.com/2014/04/stable-channel-update.html
Reference: https://code.google.com/p/chromium/issues/detail?id=350434
Reference: https://code.google.com/p/v8/source/detail?r=19834
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 hand
Bugzilla
CVE-2014-1721 v8: memory corruption issue fixed in Google Chrome 34.0.1847.116 [epel-6]
bugzilla·2014-04-10·CVSS 7.5
CVE-2014-1721 [HIGH] CVE-2014-1721 v8: memory corruption issue fixed in Google Chrome 34.0.1847.116 [epel-6]
CVE-2014-1721 v8: memory corruption issue fixed in Google Chrome 34.0.1847.116 [epel-6]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora EPEL.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When creating a Bodhi update request, please use the bodhi submission link
noted in the next comment(s). This will include the bug IDs of this
tracking bug as well as the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
Bodhi notes field when available.
epel-6 track
Bugzilla
CVE-2014-1721 v8: memory corruption issue fixed in Google Chrome 34.0.1847.116 [fedora-all]
bugzilla·2014-04-10·CVSS 7.5
CVE-2014-1721 [HIGH] CVE-2014-1721 v8: memory corruption issue fixed in Google Chrome 34.0.1847.116 [fedora-all]
CVE-2014-1721 v8: memory corruption issue fixed in Google Chrome 34.0.1847.116 [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When creating a Bodhi update request, please use the bodhi submission link
noted in the next comment(s). This will include the bug IDs of this
tracking bug as well as the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
Bodhi notes field when available.
Please note:
http://googlechromereleases.blogspot.com/2014/04/stable-channel-update.htmlhttp://lists.opensuse.org/opensuse-updates/2014-05/msg00012.htmlhttp://security.gentoo.org/glsa/glsa-201408-16.xmlhttp://www.debian.org/security/2014/dsa-2905https://code.google.com/p/chromium/issues/detail?id=350434https://code.google.com/p/v8/source/detail?r=19834http://googlechromereleases.blogspot.com/2014/04/stable-channel-update.htmlhttp://lists.opensuse.org/opensuse-updates/2014-05/msg00012.htmlhttp://security.gentoo.org/glsa/glsa-201408-16.xmlhttp://www.debian.org/security/2014/dsa-2905https://code.google.com/p/chromium/issues/detail?id=350434https://code.google.com/p/v8/source/detail?r=19834
2014-04-09
Published