ChromeWeb browser · Google
CVE-2014-1721
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGoogle 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA vulnerability in Google V8 JavaScript engine's lazy deoptimization implementation allows memory corruption when handling heap allocations of numbers outside the Small Integer (smi) range. Remote attackers can exploit this through crafted JavaScript code to cause denial of service or potentially achieve arbitrary code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
<= 34.0.1847.115CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Google Chrome versionOpen Chrome, click the menu icon (three dots) > Help > About Google Chrome, or navigate to chrome://settings/help. The version number is displayed on this page.Affected if The displayed version is 34.0.1847.115 or any version number lower than this (e.g., 34.0.1847.114, 33.x.x.x, etc.)
-
Verify version via command lineOn Windows, run 'reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Google\Update\Clients\{8A69D345-D564-463c-AFF1-A69D9E5F2BF0}" /v pv' in Command Prompt. On macOS, run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version'. On Linux, run 'google-chrome --version' or 'chromium --version'.Affected if The reported version string shows 34.0.1847.115 or a lower version number.
-
Confirm V8 engine version (optional)In Chrome, open Developer Tools (F12), go to the Console tab, and type 'v8.version()' or 'navigator.userAgent' to see the underlying V8 version embedded in Chrome's user agent string.Affected if The V8 version corresponds to Chrome 34.0.1847.115 or earlier.
A system is affected if Google Chrome version 34.0.1847.115 or any earlier version is installed, as the vulnerability exists in the V8 JavaScript engine for these versions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Google Chrome to version 34.0.1847.116 or later which contains the patched V8 engine. Ensure all systems running Chrome are updated through organizational patch management.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1721 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-1721 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data