CVE-2005-4900
Description
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
Application impact
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| chrome | {"endIncluding":"47.0.2526.111"} | |
References
- http://ia.cr/2007/474
- http://shattered.io/
- http://www.cwi.nl/news/2017/cwi-and-google-announce-first-collision-industry-security-standard-sha-1
- http://www.securityfocus.com/bid/12577
- https://arstechnica.com/security/2017/02/at-deaths-door-for-years-widely-used-sha1-function-is-now-dead/
- https://kc.mcafee.com/corporate/index?page=content&id=SB10340
- https://security.googleblog.com/2015/12/an-update-on-sha-1-certificates-in.html
- https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html
- https://sites.google.com/site/itstheshappening
- https://www.schneier.com/blog/archives/2005/02/sha1_broken.html
- https://www.schneier.com/blog/archives/2005/08/new_cryptanalyt.html
- http://ia.cr/2007/474
- http://shattered.io/
- http://www.cwi.nl/news/2017/cwi-and-google-announce-first-collision-industry-security-standard-sha-1
- http://www.securityfocus.com/bid/12577
- https://arstechnica.com/security/2017/02/at-deaths-door-for-years-widely-used-sha1-function-is-now-dead/
- https://kc.mcafee.com/corporate/index?page=content&id=SB10340
- https://security.googleblog.com/2015/12/an-update-on-sha-1-certificates-in.html
- https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html
- https://sites.google.com/site/itstheshappening
- https://www.schneier.com/blog/archives/2005/02/sha1_broken.html
- https://www.schneier.com/blog/archives/2005/08/new_cryptanalyt.html
CWEs
CWE-326 CWE-327
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.