dbcve.org
ChromeWeb browser · Google

CVE-2011-3044

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 SVG animation elements.

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

A use-after-free vulnerability exists in Google Chrome versions prior to 17.0.963.65. The flaw resides in the handling of SVG animation elements, where memory is accessed after it has been freed, potentially allowing an attacker to cause a denial of service or achieve unspecified code execution.

MitigationUpdate Google Chrome to version 17.0.963.65 or later to remediate this vulnerability. In enterprise environments, deploy the update through standard patch management processes.

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. Check Google Chrome version
    Open Chrome, click the menu icon (three dots) > Help > About Google Chrome. The version number is displayed on this page.
    Affected if Version is shown as less than 17.0.963.65 (for example, 17.0.963.60 or earlier)
  2. Check Apple Safari version
    Open Safari, click Safari in the menu bar > About Safari. The version number appears in the dialog box.
    Affected if Version is shown as less than 6.0 (for example, 5.1.x or earlier)
  3. Check Apple iTunes version
    Open iTunes, click Help > About iTunes. The version number displays in the window.
    Affected if Version is shown as less than 10.7 (for example, 10.6.x or earlier)
  4. Check Apple iOS version
    On the device, go to Settings > General > About. The Version field shows the iOS release number.
    Affected if Version is shown as less than 6.0 (for example, 5.x)
  5. Check openSUSE version
    Open a terminal and run 'cat /etc/os-release' or 'cat /etc/SuSE-release' to view the installed openSUSE version.
    Affected if Version shows 12.1 exactly

You are affected if any of your installed products match the vulnerable version ranges above and you use them to process SVG content (such as viewing SVG images or web pages containing SVG 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
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 to remediate this vulnerability. In enterprise environments, deploy the update through standard patch management processes.

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-3044 — 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-3044 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