ChromeWeb browser · Google
CVE-2014-1705
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 33.0.1750.152 on OS X and Linux and before 33.0.1750.154 on Windows, allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via unknown vectors.
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 confidenceMemory corruption vulnerability in Google V8 JavaScript engine allows remote attackers to cause denial of service or possibly achieve code execution via unknown vectors in Google Chrome before 33.0.1750.152 on OS X/Linux and before 33.0.1750.154 on Windows.
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
< 33.0.1750.152< 33.0.1750.154
Debian LinuxOperating system
= 7.0= 8.0= 12.3= 13.1CVSS 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 versionRun 'google-chrome --version' or 'chrome --version' or check 'About Google Chrome' in the browser menu. On Windows, check the executable properties. Compare the version number against 33.0.1750.152 (for OS X/Linux) or 33.0.1750.154 (for Windows).Affected if Chrome version is less than 33.0.1750.152 on OS X/Linux, or less than 33.0.1750.154 on Windows.
-
Verify V8 JavaScript engine is in useThis vulnerability is in the V8 engine which is built into Google Chrome by default. Confirm Chrome is using the V8 engine by visiting chrome://version and checking the JavaScript engine field, or simply confirm Chrome is the browser in use.Affected if Google Chrome with V8 engine is the browser in use and the version is vulnerable.
-
Check Debian system browser package versionOn Debian systems (versions 7.0 or 8.0), run 'dpkg -l | grep google-chrome' or check installed package version via 'apt-cache policy google-chrome-stable'. If using Chromium from Debian repos, check 'dpkg -l | grep chromium'.Affected if Google Chrome or Chromium package from Debian repositories version matches the vulnerable 7.0 or 8.0 release.
-
Check openSUSE system browser package versionOn openSUSE systems (versions 12.3 or 13.1), run 'rpm -qa | grep chrome' or 'zypper se google-chrome' to list installed Chrome packages and their versions.Affected if Google Chrome package from openSUSE repositories version matches the vulnerable 12.3 or 13.1 release.
The environment is affected if Google Chrome is installed with a version below 33.0.1750.152 (OS X/Linux) or below 33.0.1750.154 (Windows), or if Chrome/Chromium from Debian 7.0/8.0 or openSUSE 12.3/13.1 packages is in use.
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 data33.0.1750.15233.0.1750.154
Update Google Chrome to version 33.0.1750.152 or later on OS X/Linux, or 33.0.1750.154 or later on Windows, to patch the V8 JavaScript engine vulnerability.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1705 — 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-1705 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