dbcve.org
BlinkApplication · Google

CVE-2011-1803

MEDIUM · 6.5 CVSS v3.1 Published 2019-11-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
An issue exists in third_party/WebKit/Source/WebCore/svg/animation/SVGSMILElement.h in WebKit in Google Chrome before Blink M11 and M12 when trying to access a removed smil element.

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 · moderate confidence

Use-after-free vulnerability in WebKit's SVG SMIL animation handling (SVGSMILElement.h) where attempting to access a previously removed SMIL element can lead to memory corruption and potentially arbitrary code execution. This is a memory safety issue in the animation element lifecycle management.

MitigationUpgrade Google Chrome to Blink M11 or later versions which contain the fix for this vulnerability. Alternatively, disable or avoid SVG SMIL animations in untrusted content.

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
BlinkApplication
Affected:< m11

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
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

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. Identify the browser engine
    Open chrome://version and check if the browser is Chrome, Chromium, or another Blink-based browser. Look for 'Blink' in the user agent string or version details.
    Affected if The browser is not Blink-based (e.g., uses WebKit, Gecko, or other engines)
  2. Determine the Blink version
    In Chrome/Chromium, check chrome://version for the version number. Compare the Chromium/Chrome version to known version numbers corresponding to Blink M11. Chrome 11 and earlier correspond to Blink versions before M11.
    Affected if The installed Chrome/Chromium version is 11 or earlier (Blink versions before M11)
  3. Verify SVG SMIL animation usage
    Inspect web content being viewed or loaded. Look for <animate>, <animateTransform>, <set>, or other SMIL animation elements within SVG files. Check if any web pages visited contain SVG content with animated elements.
    Affected if SVG SMIL animations are actively being processed in the browser

The environment is affected if using a Blink-based browser (Chrome/Chromium version 11 or earlier) while processing content that contains SVG SMIL animations.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Google Chrome to Blink M11 or later versions which contain the fix for this vulnerability. Alternatively, disable or avoid SVG SMIL animations in untrusted content.

Fix this in Blink Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-1803 — 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-1803 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