CVE-2014-1721

v8: memory corruption issue fixed in Google Chrome 34.0.1847.116

Published Apr 9, 2014 CVSS 2.0 · 7.5 High EPSS 1.6% KEV · Not listed
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 solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DSA Debian DSA DSA-2905-1 chromium-browser security update
EUVD EUVD EUVD-2014-1795 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.
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
Chrome
Published
Updated
Aug 6, 2024, 9:50 AM
Reserved
Jan 29, 2014, 12:00 AM
Status
Modified
Published
Apr 9, 2014, 10:57 AM
Modified
Jun 17, 2026, 12:05 AM
Severity
Moderate
Public date
Mar 12, 2014, 12:00 AM