CVE-2010-2105
First published: Fri May 28 2010(Updated: )
Google Chrome before 5.0.375.55 does not properly follow the Safe Browsing specification's requirements for canonicalization of URLs, which has unspecified impact and remote attack vectors.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google Chrome (Trace Event) | <5.0.375.55 | |
| Google Chrome | <5.0.375.55 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2010-2105?
CVE-2010-2105 has a moderate severity rating due to its potential for exploitation via remote attack vectors.
How do I fix CVE-2010-2105?
To fix CVE-2010-2105, users should upgrade their Google Chrome browser to version 5.0.375.55 or newer.
What impact does CVE-2010-2105 have?
CVE-2010-2105 can lead to unspecified impacts that may compromise user security by not adhering to Safe Browsing specifications.
Which versions of Google Chrome are affected by CVE-2010-2105?
CVE-2010-2105 affects all versions of Google Chrome prior to 5.0.375.55.
Is there a known exploit for CVE-2010-2105?
There are no public details on specific exploits for CVE-2010-2105, but it presents remote attack vectors.
- agent/type
- agent/references
- agent/severity
- agent/weakness
- agent/author
- collector/mitre-cve
- source/MITRE
- agent/description
- agent/first-publish-date
- collector/nvd-historical
- agent/software-canonical-lookup-request
- collector/nvd-index
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/last-modified-date
- agent/source
- agent/softwarecombine
- agent/tags
- agent/event
- vendor/google
- canonical/google chrome (trace event)
- canonical/google chrome