CVE-2010-0646
Multiple integer signedness errors in factory.cc in Google V8 before r3560, as used in Google...
Multiple integer signedness errors in factory.cc in Google V8 before r3560, as used in Google Chrome before 4.0.249.89, allow remote attackers to execute arbitrary code in the Chrome sandbox via crafted use of JavaScript arrays.
Exploit likelihood
What each source reports
NVD Score used
10.0
Multiple integer signedness errors in factory.cc in Google V8 before r3560, as used in Google Chrome before 4.0.249.89, allow remote attackers to execute arbitrary code in the Chrome sandbox via crafted use of JavaScript arrays.
- Record
CVE-2010-0646- CVSS 2.0
- 10.0 High
AV:N/AC:L/Au:N/C:C/I:C/A:C - Weakness
- CWE-189
- Updated
- 2026-11-02
CVE List No score
Multiple integer signedness errors in factory.cc in Google V8 before r3560, as used in Google Chrome before 4.0.249.89, allow remote attackers to execute arbitrary code in the Chrome sandbox via crafted use of JavaScript arrays.
- Record
CVE-2010-0646- Updated
- 2026-11-02
EUVDEUVD-2010-0677 No score
Multiple integer signedness errors in factory.cc in Google V8 before r3560, as used in Google Chrome before 4.0.249.89, allow remote attackers to execute arbitrary code in the Chrome sandbox via crafted use of JavaScript arrays.
- Record
EUVD-2010-0677- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-f8xj-3764-2w44 No score
Multiple integer signedness errors in factory.cc in Google V8 before r3560, as used in Google...
Multiple integer signedness errors in factory.cc in Google V8 before r3560, as used in Google Chrome before 4.0.249.89, allow remote attackers to execute arbitrary code in the Chrome sandbox via crafted use of JavaScript arrays.
- Record
GHSA-f8xj-3764-2w44- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2010-0646 is a high vulnerability (CVSS 10.0) in Google Chrome, published February 18, 2010. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 5.12%, the 92nd percentile. No source names a fixed version.
References
exchange.xforce.ibmcloud.com/vulnerabilities/56213
oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14222
securityfocus.com/bid/38177
code.google.com/p/v8/source/detail?r=3560
sites.google.com/a/chromium.org/dev/Home/chromium-security/chromium-security-bugs
securitytracker.com/id?1023583
Show 8 moreShow less
vupen.com/english/advisories/2010/0361
code.google.com/p/chromium/issues/detail?id=31009
osvdb.org/62316
googlechromereleases.blogspot.com/2010/02/stable-channel-update.html
codereview.chromium.org/525064
secunia.com/advisories/38545
nvd.nist.gov/vuln/detail/CVE-2010-0646
github.com/advisories/GHSA-f8xj-3764-2w44