ChromeWeb browser · Google
CVE-2013-6655
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 Blink, as used in Google Chrome before 33.0.1750.117, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to improper handling of overflowchanged DOM events during interaction between JavaScript and layout.
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 confidenceUse-after-free vulnerability in Blink rendering engine (used by Chrome before 33.0.1750.117) where improper handling of overflowchanged DOM events during JavaScript-layout interaction leads to freed memory being accessed. This can cause denial of service or potentially enable 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
<= 33.0.1750.116= 33.0.1750.0= 33.0.1750.1= 33.0.1750.2= 33.0.1750.3= 33.0.1750.4= 33.0.1750.5= 33.0.1750.6= 33.0.1750.7= 33.0.1750.8= 33.0.1750.9= 33.0.1750.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
- 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 if Google Chrome is installedLocate Chrome executable - on Windows check C:\Program Files\Google\Chrome\Application\chrome.exe, on macOS check /Applications/Google Chrome.app, or on Linux check /usr/bin/google-chrome or /usr/bin/chromium-browserAffected if Google Chrome browser is present on the system
-
Determine Google Chrome versionOpen Chrome and navigate to chrome://version, or from command line run 'google-chrome --version' on Linux, or check Help > About Google Chrome in the application menuAffected if The displayed version number is 33.0.1750.116 or lower, or matches any of the specific affected versions 33.0.1750.0 through 33.0.1750.10
-
Compare against fixed versionThe patched version is 33.0.1750.117 - compare your installed version number to this thresholdAffected if Installed version is less than 33.0.1750.117 (any version from 33.0.1750.0 through 33.0.1750.116)
A user is affected if Google Chrome version 33.0.1750.116 or any version from 33.0.1750.0 through 33.0.1750.10 is installed, since the vulnerability exists in all versions before 33.0.1750.117.
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 33.0.1750.117 or later. For legacy systems that cannot update, consider isolating the browser in a sandboxed environment or replacing with a supported browser version.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6655 — 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-6655 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