CVE-2010-4033 json
Google Chrome before 7.0.517.41 does not properly implement the autofill and autocomplete functionality, which allows remote attackers to c…
published 2010-10-21 16 y ago modified 2026-06-16 4 mo ago also EUVD-2010-4009
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 0
- none known
Summary
Google Chrome before 7.0.517.41 does not properly implement the autofill and autocomplete functionality, which allows remote attackers to conduct "profile spamming" attacks via unspecified vectors.
Patch / fix
- google chrome 7.0.517.41
Exploit prediction
1.21% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Technology feeds
References
-
vupen.com
/english/advisories/2010/2731
vdb-entry, vendor-advisory
-
secunia.com
/advisories/41888
third-party-advisory, vendor-advisory
- code.google.com /p/chromium/issues/detail?id=48225
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A7159
vdb-entry, signature
- code.google.com /p/chromium/issues/detail?id=51727
-
securityfocus.com
/bid/44241
vdb-entry
- googlechromereleases.blogspot.com /2010/10/stable-channel-update.html
Sources
- CVE List CVE-2010-4033
- NVD CVE-2010-4033
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.