dbcve.org
ChromeWeb browser · Google

CVE-2011-3969

MEDIUM · 6.8 CVSS v2.0 Published 2012-02-09
Fix available
A fix is available. Upgrade to 6.0 / 10.7 or later.
See remediation →
77/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
Use-after-free vulnerability in Google Chrome before 17.0.963.46 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to layout of SVG documents.

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 use-after-free vulnerability exists in Google Chrome's rendering engine when processing SVG document layouts. The flaw allows remote attackers to potentially execute arbitrary code or cause denial of service by freeing memory that is still being accessed during SVG layout operations.

MitigationUpdate Google Chrome to version 17.0.963.46 or later to apply the security patch. If immediate patching is not feasible, consider restricting or disabling SVG rendering in untrusted contexts until the update can be deployed.

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:< 17.0.963.46
SafariWeb browser
Affected:< 6.0
ItunesApplication
Affected:< 10.7
Iphone OsOperating system
Affected:< 6.0

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/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. Identify installed browsers and Apple software
    Check if Google Chrome, Apple Safari, Apple iTunes, or Apple iOS are installed on the system or device. On Windows, look in Program Files (Chrome) or Program Files (x86) (iTunes). On macOS, check /Applications for Safari and iTunes. On iOS, check the device settings.
    Affected if Any of these products are present on the system or device
  2. Check Google Chrome version
    Open Chrome, click the menu icon (three dots), select Help, then About Google Chrome. The version number will be displayed on that page.
    Affected if The version displayed is earlier than 17.0.963.46
  3. Check Apple Safari version
    Open Safari, click Safari in the menu bar, then select About Safari. The version number will be displayed.
    Affected if The version displayed is earlier than 6.0
  4. Check Apple iTunes version
    Open iTunes, click Help in the menu bar, then select About iTunes. The version number will be displayed.
    Affected if The version displayed is earlier than 10.7
  5. Check Apple iOS version (iPhone/iPad)
    On the device, go to Settings > General > About. The version number is displayed next to Version.
    Affected if The version displayed is earlier than 6.0
  6. Verify SVG rendering is enabled
    In Chrome, go to chrome://settings, search for 'SVG' or check content settings. In Safari, SVG is enabled by default but can be disabled via preferences. For the vulnerability to apply, SVG content must be allowed to render in the browser.
    Affected if SVG rendering is enabled and a vulnerable version of Chrome or Safari is installed

The user is affected if any of the listed products (Chrome, Safari, iTunes, iOS) are installed with versions below the specified thresholds and SVG content can be rendered in that browser.

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 6.0 / 10.7 / 17.0.963.46 or later
Fixed in 6.010.717.0.963.46
Interim mitigation

Update Google Chrome to version 17.0.963.46 or later to apply the security patch. If immediate patching is not feasible, consider restricting or disabling SVG rendering in untrusted contexts until the update can be deployed.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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