CVE-2014-1721 Memory corruption in n/a

What is CVE-2014-1721?

CVE-2014-1721 is a high-severity memory corruption vulnerability in Google Chrome, published on 9 Apr 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

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

Weakness: CWE-189

Which versions are affected by CVE-2014-1721?

It affects 1 product.

Products include Google Chrome.

How do I fix CVE-2014-1721?

Upgrade to a fixed version.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2014-1721 being exploited?

There is no known exploitation of CVE-2014-1721 in the wild and no public exploit code.

Other vulnerabilities in Google Chrome

• CVE-2022-4135 Google Chromium GPU Heap Buffer Overflow Exploited Critical 9.6
• CVE-2020-16017 Google Chrome Use-After-Free Exploited Critical 9.6
• CVE-2020-16010 Google Chrome for Android UI Heap Buffer Overflow Exploited Critical 9.6
• CVE-2026-87491 Google Chromium V8 Out of Bounds Write Exploited High 8.8
• CVE-2026-85046 Google Chromium V8 Type Confusion Exploited High 8.8

All Google Chrome vulnerabilities

Sources

• CVE record
• NVD
• OSV
• GitHub advisory
• How this page is made

Also known as GHSA-fqrm-g3fv-x64c, UBUNTU-CVE-2014-1721.