CVE-2011-3966 json
Use-after-free vulnerability in Google Chrome before 17.0.963.46 allows remote attackers to cause a denial of service or possibly have unsp…
published 2012-02-09 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-3919
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
Use-after-free vulnerability in Google Chrome before 17.0.963.46 allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to error handling for Cascading Style Sheets (CSS) token-sequence data.
Patch / fix
- google chrome 17.0.963.46
- apple itunes 10.7
- apple safari 6.0
- apple iphone_os 6.0
- chromium openSUSE Tumbleweed 55.0.2883.75-3.1
- chromium openSUSE Tumbleweed 113.0.5672.92-1.1
opensuse advisories openSUSE-SU-2024:10171-1openSUSE-SU-2024:12948-1
Exploit prediction
2.11% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
-
lists.apple.com
/archives/security-announce/2012/Sep/msg00003.html
vendor-advisory
-
lists.apple.com
/archives/security-announce/2012/Sep/msg00001.html
vendor-advisory
-
lists.apple.com
/archives/security-announce/2012/Jul/msg00000.html
vendor-advisory
- support.apple.com /kb/HT5485
- support.apple.com /kb/HT5503
- googlechromereleases.blogspot.com /2012/02/stable-channel-update.html
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14944
vdb-entry, signature
- code.google.com /p/chromium/issues/detail?id=109716
- support.apple.com /kb/HT5400
Sources
- CVE List CVE-2011-3966
- NVD CVE-2011-3966
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.