CVE-2011-2336
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 · uneditedAn issue exists in WebKit in Google Chrome before Blink M12. when clearing lists in AnimationControllerPrivate that signal when a hardware animation starts.
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 · low confidenceUse-after-free or race condition vulnerability in WebKit's AnimationControllerPrivate when clearing lists that signal hardware animation start. The issue exists in Google Chrome versions prior to Blink M12, where improper list management during animation controller cleanup can lead to memory corruption or incorrect state.
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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 installed Chrome/Blink versionNavigate to chrome://version in the Chrome browser or check the browser's About information to find the full version string including the Blink revision numberAffected if The Blink version number is less than M12 (for example, M11, M10, or earlier)
-
Determine if hardware acceleration is enabledNavigate to chrome://settings and locate the 'Hardware acceleration' or 'Use hardware acceleration when available' setting in the Advanced or System sectionAffected if Hardware acceleration is enabled - the vulnerability specifically occurs when clearing lists that signal hardware animation start
-
Review browser crash logs for AnimationControllerPrivate errorsAccess crash reports through chrome://crashes or check system event logs for crashes occurring in WebKit or AnimationController componentsAffected if Crashes reference AnimationControllerPrivate, list clearing operations, or memory corruption during animation cleanup
-
Check for abnormal animation-related behaviorObserve the browser for unexpected crashes, freezing, or memory errors when websites with animated content (CSS animations, transitions, or hardware-accelerated graphics) are loadedAffected if The browser exhibits instability, crashes, or memory errors specifically when viewing animated content
A user is affected if their Chrome/Blink version is earlier than M12 AND hardware acceleration is enabled, as the use-after-free occurs during hardware animation list cleanup.
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 Chrome to version Blink M12 or later. If immediate patching is not possible, consider restricting access to hardware-accelerated animations or using alternative browsers until the update can be applied.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2336 — 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-2336 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