Skip to content
Fencer Intel
critical 9.3

CVE-2010-3412 in the critical feed json

Race condition in the console implementation in Google Chrome before 6.0.472.59 has unspecified impact and attack vectors.

published 16y ago modified 4mo ago also EUVD-2010-3410

cvss
9.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits
0
none known

Summary

Race condition in the console implementation in Google Chrome before 6.0.472.59 has unspecified impact and attack vectors.

Patch / fix

  • google chrome 6.0.472.59

Is CVE-2010-3412 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 Fencer

Exploit prediction

0.60% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization
Technology feeds

References

Sources

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.