ChromeWeb browser · Google
CVE-2011-3051
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 · uneditedUse-after-free vulnerability in the Cascading Style Sheets (CSS) implementation in Google Chrome before 17.0.963.83 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to the cross-fade function.
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 confidenceUse-after-free memory corruption vulnerability in Google Chrome's Cascading Style Sheets (CSS) implementation, specifically in the cross-fade function. This memory safety flaw allows remote attackers to potentially execute arbitrary code or cause denial of service by exploiting freed memory that is still referenced.
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
< 17.0.963.83= 12.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Google Chrome versionNavigate to chrome://version in the Chrome browser or go to Help > About Google Chrome. Record the version number shown.Affected if The version is less than 17.0.963.83 (for example, 17.0.963.56, 16.x.x.x, etc.)
-
Verify Chrome version via command lineOn Windows, run 'reg query "HKEY_CURRENT_USER\Software\Google\Chrome\BLFeature' or check the executable properties. On Linux, run 'google-chrome --version' or 'chromium-browser --version'. On macOS, run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version'.Affected if The reported version number is below 17.0.963.83
-
Confirm cross-fade CSS function usageReview any web applications or internal sites hosted in the environment that may utilize the CSS cross-fade() function. This function is part of the CSS Image Values and Replaced Content module.Affected if The browser loads web content containing cross-fade() CSS function while running an affected Chrome version below 17.0.963.83
-
Check OpenSUSE version if applicableIf running Chrome on OpenSUSE 12.1, run 'cat /etc/os-release' or 'lsb_release -a' to confirm the OS version.Affected if Running OpenSUSE 12.1 with Google Chrome version below 17.0.963.83
You are affected if Google Chrome version is below 17.0.963.83 AND the browser is used to render web content that could contain the CSS cross-fade function.
Generated from the published advisory. Verify against your own configuration.
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 data17.0.963.83
Update Google Chrome to version 17.0.963.83 or later. Organizations should deploy browser updates through their enterprise patch management infrastructure and verify the update completes successfully across managed endpoints.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3051 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-3051 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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