dbcve.org
ChromeWeb browser · Google

CVE-2011-1793

HIGH · 7.5 CVSS v2.0 Published 2014-12-26
Fix available
A fix is available. Upgrade to after 11.0.696.65 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
rendering/svg/RenderSVGResourceFilter.cpp in WebCore in WebKit in Google Chrome before 11.0.696.65 allows remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted SVG document that leads to a "stale pointer."

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 confidence

A stale pointer vulnerability exists in WebKit's SVG filter rendering code (RenderSVGResourceFilter.cpp) in Google Chrome versions prior to 11.0.696.65. When processing a specially crafted SVG document, the application references a stale pointer, leading to memory corruption that can cause a denial of service (crash) or potentially allow arbitrary code execution.

MitigationUpgrade Google Chrome to version 11.0.696.65 or later to obtain the patch that addresses the stale pointer issue in SVG filter processing.

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
Affected:<= 11.0.696.65

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Google Chrome version
    Open Chrome, click the wrench icon (or three-dot menu in newer versions), select 'About Google Chrome' to view the current version number displayed on the page
    Affected if The displayed version number is less than or equal to 11.0.696.65 (for example, 11.0.696.64, 10.x, 9.x, etc.)
  2. Verify Chrome version via command line
    Open Command Prompt or Terminal and run: chrome --version (or on Windows: "C:\Program Files\Google\Chrome\Application\chrome.exe" --version)
    Affected if The version output shows a number lower than 11.0.696.65
  3. Confirm SVG filter usage in your environment
    Check if you or your users open or render SVG files or web pages containing SVG filter effects - no specific configuration check is needed as this is a code-level flaw triggered by processing malicious SVG content
    Affected if Chrome version is <= 11.0.696.65 AND the browser processes SVG content from untrusted sources (which is common in normal web browsing)

You are affected if your installed Google Chrome version is 11.0.696.65 or any earlier version (e.g., 10.x, 9.x).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 11.0.696.65
Interim mitigation

Upgrade Google Chrome to version 11.0.696.65 or later to obtain the patch that addresses the stale pointer issue in SVG filter processing.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-1793 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2011-1793 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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