CVE-2010-4576 json
browser/worker_host/message_port_dispatcher.cc in Google Chrome before 8.0.552.224 and Chrome OS before 8.0.552.343 does not properly handl…
published 2010-12-22 15 y ago modified 2026-06-16 4 mo ago also EUVD-2010-4542
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
browser/worker_host/message_port_dispatcher.cc in Google Chrome before 8.0.552.224 and Chrome OS before 8.0.552.343 does not properly handle certain postMessage calls, which allows remote attackers to cause a denial of service (NULL pointer dereference and application crash) via crafted JavaScript code that creates a web worker.
Patch / fix
- google chrome 8.0.552.224
- google chrome_os 8.0.552.343
Exploit prediction
1.67% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- code.google.com http://code.google.com/p/chromium/issues/detail?id=63529 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
- Technology feeds
References
-
src.chromium.org
/viewvc/chrome?view=rev&revision=66620
patch, vendor-advisory
-
code.google.com
/p/chromium/issues/detail?id=63529
exploit, patch, vendor-advisory
-
gentoo.org
/security/en/glsa/glsa-201012-01.xml
vendor-advisory, third-party-advisory
-
googlechromereleases.blogspot.com
/2010/12/stable-beta-channel-updates_13.html
vendor-advisory
-
secunia.com
/advisories/42648
third-party-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14161
vdb-entry, signature, third-party-advisory
-
securityfocus.com
/bid/45390
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2010-4576
- NVD CVE-2010-4576
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.