ChromeWeb browser · Google
CVE-2013-6654
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 · uneditedThe SVGAnimateElement::calculateAnimatedValue function in core/svg/SVGAnimateElement.cpp in Blink, as used in Google Chrome before 33.0.1750.117, does not properly handle unexpected data types, which allows remote attackers to cause a denial of service (incorrect cast) 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 confidenceThe vulnerability exists in Blink's SVGAnimateElement::calculateAnimatedValue function which fails to properly validate or handle unexpected data types before performing a cast operation, leading to type confusion that causes a denial of service or potentially other unspecified impact.
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.
-
Verify Google Chrome is installedCheck for Google Chrome installation by looking for chrome.exe in typical installation paths (e.g., C:\Program Files\Google\Chrome\Application\chrome.exe on Windows, /Applications/Google Chrome.app on macOS, or via package manager on Linux)Affected if Google Chrome is not installed on the system
-
Retrieve installed Chrome versionOpen Google Chrome, navigate to chrome://settings/help, or use the command line: 'chrome --version' (Linux) or right-click the Chrome shortcut and select Properties to view the versionAffected if Unable to determine the installed Chrome version
-
Compare version against affected rangeCompare the installed version number to the affected range: 33.0.1750.0 through 33.0.1750.116. The vulnerability affects versions <= 33.0.1750.116Affected if The installed version is 33.0.1750.116 or lower, meaning the SVGAnimateElement::calculateAnimatedValue type confusion vulnerability is present
A user is affected if Google Chrome version 33.0.1750.116 or lower is installed, as this version contains the vulnerable Blink rendering engine with the type confusion flaw in SVG animation processing.
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 to obtain the patched Blink rendering engine that properly handles data type validation in SVG animation processing.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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-6654 — 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-6654 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