CVE-2010-0657 in the critical feed json
Google Chrome before 4.0.249.78 on Windows does not perform the expected encoding, escaping, and quoting for the URL in the --app argument…
published 2010-02-18 16 y ago modified 2026-06-16 4 mo ago also EUVD-2010-0688
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
Google Chrome before 4.0.249.78 on Windows does not perform the expected encoding, escaping, and quoting for the URL in the --app argument in a desktop shortcut, which allows user-assisted remote attackers to execute arbitrary programs or obtain sensitive information by tricking a user into creating a crafted shortcut.
Patch / fix
- google chrome 4.0.249.78
Exploit prediction
1.88% chance of exploitation in the next 30 days, higher than 79% 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
- Technology feeds
References
- googlechromereleases.blogspot.com /2010/01/stable-channel-update_25.html
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14306
vdb-entry, signature
-
securitytracker.com
/id?1023506
vdb-entry
- sites.google.com /a/chromium.org/dev/Home/chromium-security/chromium-security-bugs
- code.google.com /p/chromium/issues/detail?id=23693
Sources
- CVE List CVE-2010-0657
- NVD CVE-2010-0657
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.