CVE-2011-2335
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 · uneditedA double-free vulnerability exists in WebKit in Google Chrome before Blink M12 in the WebCore::CSSSelector 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 · moderate confidenceA double-free vulnerability in WebCore::CSSSelector in WebKit allows memory corruption that could be exploited for arbitrary code execution. The flaw occurs during CSS selector parsing in affected versions of Google Chrome before the Blink M12 fork.
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< m12CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Identify the browser or application using Blink/WebKitDetermine if your application embeds or uses Google Chrome, Chromium, or a WebKit-based browser for rendering web content. Check the application's 'About' or version information panel.Affected if The application uses any Chromium-based browser or embeds the WebKit/Blink rendering engine for CSS parsing.
-
Determine the Blink versionAccess the browser's version information (typically via chrome://version or the application's About/Help menu). Look for the Blink version number in the user agent string or version details.Affected if The Blink version is earlier than M12, or the version string indicates a pre-fork WebKit build (Chrome versions prior to the Blink fork in 2013).
-
Confirm CSS selector parsing is activeThe vulnerability triggers during CSS selector parsing, which is a core browser function enabled by default. No specific configuration check is needed - any page loading CSS content will exercise this code path.Affected if The browser renders web pages with CSS stylesheets, which is the default behavior for any WebKit/Blink-based browser.
-
Check for known browser build identifiersIn the browser version string, look for build dates or version numbers. Earlier Chrome builds (pre-2013) used WebKit; builds from 2013 onward use the forked Blink engine.Affected if The build predates the April 2013 Blink fork (Chrome versions before approximately 28), indicating the vulnerable WebKit codebase is in use.
You are affected if your Chromium-based browser or embedded WebKit/Blink engine version is earlier than the M12 fork (approximately Chrome 28, released April 2013), as this double-free in CSSSelector was present in the pre-Blink WebKit code.
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 dataUpdate Google Chrome/Chromium to a version after Blink M12 (or latest stable) to receive the patched WebKit/Blink engine. For embedded WebKit implementations, apply the upstream patch to the CSSSelector code path.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2335 — 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-2335 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