ChromeWeb browser · Google
CVE-2014-1719
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 · uneditedUse-after-free vulnerability in the WebSharedWorkerStub::OnTerminateWorkerContext function in content/worker/websharedworker_stub.cc in the Web Workers implementation in Google Chrome before 34.0.1847.116 allows remote attackers to cause a denial of service (heap memory corruption) or possibly have unspecified other impact via vectors that trigger a SharedWorker termination during script loading.
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 use-after-free vulnerability in Google Chrome's Web Workers implementation (WebSharedWorkerStub::OnTerminateWorkerContext) allows remote attackers to corrupt heap memory or potentially achieve arbitrary code execution by triggering SharedWorker termination during script loading, affecting versions prior to 34.0.1847.116.
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.
-
Verify Google Chrome is installedCheck for Chrome executable: on Windows look in Program Files\Google\Chrome\Application\ or run 'chrome://version' in the browser; on Mac check /Applications/Google Chrome.app; on Linux check /opt/google/chrome/ or run 'google-chrome --version'Affected if Google Chrome browser is present on the system
-
Determine installed Chrome versionNavigate to chrome://version in the browser address bar or run 'google-chrome --version' from command line; the version number is displayed prominentlyAffected if Unable to determine version or Chrome is not installed
-
Compare version against affected rangeCompare your installed version number to the affected range: any version less than or equal to 34.0.1847.115 is vulnerableAffected if Installed version is 34.0.1847.115 or earlier (versions prior to 34.0.1847.116)
-
Confirm SharedWorker API is accessibleThe vulnerability affects SharedWorker functionality which is a standard Web API enabled by default in Chrome; visit any webpage using SharedWorker or check if chrome://inspect/#workers shows worker endpointsAffected if SharedWorker is in use on Chrome versions within the affected range (the feature is enabled by default, so this condition is trivially met for vulnerable versions)
You are affected if Google Chrome is installed with any version <= 34.0.1847.115, as the use-after-free flaw in WebSharedWorkerStub::OnTerminateWorkerContext triggers during SharedWorker termination which is a standard browser feature.
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 dataUpdate Google Chrome to version 34.0.1847.116 or later to patch this vulnerability; organizations should ensure automated browser updates are enabled or deploy the patched version via their endpoint management systems.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1719 — 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-1719 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