dbcve.org
ChromeWeb browser · Google

CVE-2011-3034

MEDIUM · 6.8 CVSS v2.0 Published 2012-03-05
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.65 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors involving an SVG document.

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

Use-after-free vulnerability in Google Chrome's SVG document handling before version 17.0.963.65. The flaw allows remote attackers to cause denial of service or possibly execute arbitrary code by tricking users into visiting malicious web pages containing specially crafted SVG content.

MitigationUpdate Google Chrome to version 17.0.963.65 or later. No configuration-based workarounds exist for this client-side browser vulnerability.

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.65
SafariWeb browser
Affected:< 6.0
OpensuseOperating system
Affected:= 12.1
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 your browser/product
    Determine which affected product is installed: Google Chrome, Apple Safari, Apple iTunes, or the iOS version on iPhone/iPad. Check the installed application.
    Affected if Any of these affected products are installed on the system.
  2. Check Google Chrome version
    Open Chrome, click the three-dot menu, go to Help > About Google Chrome, or navigate to chrome://version. Compare the version number to 17.0.963.65.
    Affected if The installed Chrome version is lower than 17.0.963.65.
  3. Check Apple Safari version
    Open Safari, go to Safari > About Safari. Compare the version to 6.0.
    Affected if The installed Safari version is lower than 6.0.
  4. Check Apple iTunes version
    Open iTunes, go to Help > About iTunes. Compare the version to 10.7.
    Affected if The installed iTunes version is lower than 10.7.
  5. Check iOS version on iPhone/iPad
    Go to Settings > General > About > Version on the iOS device. Compare to 6.0.
    Affected if The iOS version is lower than 6.0.

You are affected if any of these products are installed and their versions fall below the specified thresholds, as the vulnerability can be triggered by visiting a malicious web page with specially crafted SVG content.

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.65 or later
Fixed in 6.010.717.0.963.65
Interim mitigation

Update Google Chrome to version 17.0.963.65 or later. No configuration-based workarounds exist for this client-side browser vulnerability.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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