Security readout for executives and security teams
Plain-English summary
This is an old memory-safety flaw in Google Chrome’s WebKit code before Blink M12. A vulnerable browser could mishandle CSS selector data and free memory twice. The provided sources do not give a severity score, confirmed impact, exploit status, or a specific fixed release beyond the affected range.
Executive priority
Treat as a legacy exposure cleanup item unless affected Chrome builds are found. If obsolete Chrome exists in production or user-accessible systems, prioritize removal because browser memory-safety flaws can become high-impact when exposed to untrusted web content.
Technical view
CVE-2011-2335 describes a double-free in WebKit’s WebCore::CSSSelector function affecting Google Chrome before Blink M12. The bundle links Chromium issue 81351 and WebKit changeset 80155 but does not provide CVSS, CWE, exploitability details, or operational mitigations.
Likely exposure
Exposure appears limited to systems still running Google Chrome before Blink M12. The provided sources do not name other affected products. Legacy managed desktops, archived VMs, or old browser test images should be checked if they may retain obsolete Chrome builds.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. The memory-corruption class is concerning, but the supplied evidence does not establish practical exploitability, exploitation in the wild, or required user interaction.
Researcher notes
Key gaps are CVSS, CWE, exploitability details, and precise fixed-version language. Analysis should stay tied to the named affected product and range: Google Chrome before Blink M12. Do not infer active exploitation from the vulnerability class alone.
Mitigation direction
- Inventory endpoints for Google Chrome builds before Blink M12.
- Upgrade affected Chrome installations to supported vendor-maintained releases.
- Remove obsolete Chrome binaries from legacy images and test systems.
- Check Chromium or vendor guidance for any version-specific remediation notes.
Validation and detection
- Confirm Chrome versions installed across managed endpoints and golden images.
- Flag any Chrome build identified as before Blink M12.
- Review legacy VM and kiosk images for obsolete browser packages.
- Document absence or presence of affected Chrome versions in vulnerability records.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2011-2335 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://bugs.chromium.org/p/chromium/issues/detail?id=81351CVE reference · x_refsource_MISC
- https://trac.webkit.org/changeset/80155/webkitCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.