Vulnerabilities · 2005 · Google
CVE-2005-4900
Google Chrome vulnerability
SHA-1 is not collision resistant, which makes it easier for context-dependent attackers to conduct spoofing attacks, as demonstrated by attacks on the use of SHA-1 in TLS 1.2. NOTE: this CVE exists to provide a common identifier for referencing this SHA-1 issue; the existence of an identifier is not, by itself, a technology recommendation.
Affected products
Chrome. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Google Chrome runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- ia.cr/2007/474 · Third Party Advisory
- security.googleblog.com/2015/12/an-update-on-sha-1-certificates-in.html · Third Party Advisory
- sites.google.com/site/itstheshappening · Third Party Advisory
- www.schneier.com/blog/archives/2005/02/sha1_broken.html · Third Party Advisory
- www.schneier.com/blog/archives/2005/08/new_cryptanalyt.html · Third Party Advisory
- shattered.io/
- www.cwi.nl/news/2017/cwi-and-google-announce-first-collision-industry-security-standard-sh
- www.securityfocus.com/bid/12577
- nvd.nist.gov/vuln/detail/CVE-2005-4900
- cve.org/CVERecord?id=CVE-2005-4900
More vulnerabilities in Google products
CVE-2026-28615CVE-2026-28587CVE-2026-28576CVE-2026-28575CVE-2026-20418CVE-2026-20417CVE-2026-20415CVE-2026-20414All 12,443
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.