ChromeWeb browser · Google
CVE-2013-2847
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 · uneditedRace condition in the workers implementation in Google Chrome before 27.0.1453.93 allows remote attackers to cause a denial of service (use-after-free and application crash) 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 confidenceRace condition in Google Chrome's Web Workers implementation allows remote attackers to trigger a use-after-free vulnerability, potentially causing denial of service through application crashes or possibly achieving unspecified other impact via unknown vectors.
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
<= 27.0.1453.91= 27.0.1453.0= 27.0.1453.1= 27.0.1453.2= 27.0.1453.3= 27.0.1453.4= 27.0.1453.5= 27.0.1453.6= 27.0.1453.7= 27.0.1453.8= 27.0.1453.9= 27.0.1453.10CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Identify Chrome installationOn Windows, check Program Files/Google/Chrome/Application/chrome.exe or run 'chrome --version'. On macOS, run '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --version' or check About Google Chrome. On Linux, run 'google-chrome --version' or 'chromium-browser --version'.Affected if Google Chrome is installed on the system.
-
Retrieve installed Chrome version numberNavigate to chrome://settings/help in the Chrome browser, or run 'chrome --version' from command line. Note the full version string (for example: 27.0.1453.93).Affected if A Chrome version is detected.
-
Compare installed version against affected rangeCheck if the installed version matches 27.0.1453.0 through 27.0.1453.10, or is less than or equal to 27.0.1453.91. These specific versions are listed as affected in the CVE.Affected if The installed version is 27.0.1453.0 through 27.0.1453.10, or is <= 27.0.1453.91.
-
Determine if Web Workers are in useReview application code or web traffic for usage of the Web Workers JavaScript API (new Worker(), SharedWorker). Check if any web applications loaded in Chrome create worker threads.Affected if The installed Chrome version is within the affected range AND the browser is used to run applications utilizing Web Workers.
A user is affected if they are running Google Chrome version 27.0.1453.0 through 27.0.1453.10 (or any version <= 27.0.1453.91) and use the browser to execute web applications that employ Web Workers.
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 27.0.1453.93 or later to remediate this vulnerability in the workers implementation.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2847 — 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-2013-2847 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