dbcve.org
ChromeWeb browser · Google

CVE-2011-1800

HIGH · 7.5 CVSS v2.0 Published 2011-05-16
Fix available
A fix is available. Upgrade to 11.0.696.71 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
Multiple integer overflows in the SVG Filters implementation in WebCore in WebKit in Google Chrome before 11.0.696.68 allow remote attackers to cause a denial of service 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 · moderate confidence

Integer overflows in the SVG Filters implementation within WebCore (WebKit) in Google Chrome allow attackers to trigger heap corruption or memory safety violations by processing specially crafted SVG filter operations. The overflows occur when calculating buffer sizes or memory offsets for SVG filter primitives, potentially enabling remote code execution or denial of service.

MitigationUpgrade Google Chrome to version 11.0.696.68 or later. Organizations using WebKit-based browsers or embedding WebKit should apply corresponding security updates and monitor for subsequent CVEs addressing this code path.

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.71

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. Confirm Google Chrome is installed
    Open Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' or 'chrome --version' from command line
    Affected if Google Chrome browser is present on the system
  2. Check Chrome version number
    In Chrome, go to chrome://settings/help to view the version. From command line, run: google-chrome --version or chrome --version
    Affected if The displayed version is lower than 11.0.696.71
  3. Verify SVG filter processing is possible
    SVG filters are a built-in feature of Chrome's WebKit rendering engine and are enabled by default for processing SVG content. No configuration check required.
    Affected if Chrome renders or processes SVG content from untrusted sources (e.g., visiting web pages, opening SVG files)

User is affected if Google Chrome version is below 11.0.696.71 and the browser is used to render or process SVG content from untrusted sources.

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 11.0.696.71 or later
Fixed in 11.0.696.71
Interim mitigation

Upgrade Google Chrome to version 11.0.696.68 or later. Organizations using WebKit-based browsers or embedding WebKit should apply corresponding security updates and monitor for subsequent CVEs addressing this code path.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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