CVE-2014-1721 - CVE House
Back to Database
Status published High CVE-2014-1721

Google V8, as used in Google Chrome before 34.0.1847.116, does...

Vulnerability 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.

Impact Analysis

Refer to official advisory for detailed impact metrics.

Remediation

Ensure systems are updated to the latest vendor-supplied patch levels.

THREAT MONITOR

Am I Vulnerable?

Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2014-1721

Credits & Attribution

No credits recorded in the NVD database.

References

More from google

View All →
CVE-2025-24959
Environment Variable Injection for dotenv API in zx
Low 1
CVE-2024-45601
Local file Inclusion via static file serving functionality in Mesop
High 7.5
CVE-2022-3708
Web Stories <= 1.24.0 - Server Side Request Forgery
Critical 9.6
CVE-2022-31055
Improper Access Control in kctf
High 7.5
CVE-2022-23569
`CHECK`-fails when building invalid tensor shapes in Tensorflow
Medium 6.5

Affected Vendor

Affected Software

chrome
Vulnerable Versions:
0

Timeline

Official Publish: April 9th, 2014
Last Modified: August 6th, 2024
Added to House: July 19th, 2026

CVSS Vectors

Weaknesses (CWE)

No CWE data available

MITRE ATT&CK TTPs

No associated TTPs found for this vulnerability.