CVE-2010-1506 json
The Google V8 bindings in Google Chrome before 4.1.249.1059 allow attackers to cause a denial of service (memory corruption) via unknown ve…
published 16y ago modified 4mo ago also EUVD-2010-1533
- cvss
- 7.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
The Google V8 bindings in Google Chrome before 4.1.249.1059 allow attackers to cause a denial of service (memory corruption) via unknown vectors.
Patch / fix
- google chrome 4.1.249.1059
Is CVE-2010-1506 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.10% chance of exploitation in the next 30 days, higher than 65% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.8 | AV:N/AC:L/Au:N/C:N/I:N/A:C |
Classification
- Technology feeds
References
-
secunia.com
/advisories/39544
third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/39603
vdb-entry
-
osvdb.org
/63996
vdb-entry
- googlechromereleases.blogspot.com /2010/04/stable-update-security-fixes.html
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11925
vdb-entry, signature
- bugs.chromium.org /40635
Sources
- CVE List CVE-2010-1506
- NVD CVE-2010-1506
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.
CPEs and fixed versions use Anchore's correction of NVD's data: Consolidate version ranges.