ChromeWeb browser · Google
CVE-2013-6663
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 SVGImage::setContainerSize function in core/svg/graphics/SVGImage.cpp in the SVG implementation in Blink, as used in Google Chrome before 33.0.1750.146, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to the resizing of a view.
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 the SVGImage::setContainerSize function in Blink's SVG implementation (core/svg/graphics/SVGImage.cpp). The issue occurs when resizing a view, where memory for an SVG container is freed but the pointer remains in use, potentially leading to arbitrary code execution or denial of service.
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.144= 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 Google Chrome versionOpen Chrome, click the menu icon (three dots), select Help, then About Google Chrome. The version number is displayed on that page.Affected if The version shown is 33.0.1750.0 through 33.0.1750.144 inclusive, or any version <= 33.0.1750.144 that starts with 33.0.1750.
-
Verify SVG rendering is in useConfirm that the Chrome browser has the capability to render SVG content. This is enabled by default in Chrome; no configuration change is needed.Affected if SVG rendering is enabled (default state) - the vulnerability exists in the SVGImage component itself when handling container resize events.
-
Confirm vulnerability trigger conditionThe flaw occurs when an SVG image is displayed in a view that gets resized. Any web page or application embedding SVG content that triggers a resize operation would exercise this code path.Affected if The browser displays SVG content and that content undergoes a resize operation while the page is loaded.
A user is affected if they are running Google Chrome versions 33.0.1750.0 through 33.0.1750.144 (or any version <= 33.0.1750.144 in the 33.0.1750.x branch) and view SVG content that undergoes resizing.
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.146 or later. Organizations using embedded Blink/Chromium should obtain and apply the corresponding upstream patch to SVGImage.cpp.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-6663 — 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-6663 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