CVE-2005-4900
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 5.9epss 0.9%
exploitation probability
0.9%top 41% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Affected products
n/a · n/aReferences
http://ia.cr/2007/474https://arstechnica.com/security/2017/02/at-deaths-door-for-years-widely-used-sha1-function-is-now-dead/http://shattered.io/https://kc.mcafee.com/corporate/index?page=content&id=SB10340https://security.googleblog.com/2015/12/an-update-on-sha-1-certificates-in.htmlhttps://security.googleblog.com/2017/02/announcing-first-sha1-collision.htmlhttps://sites.google.com/site/itstheshappeninghttps://www.schneier.com/blog/archives/2005/02/sha1_broken.htmlhttps://www.schneier.com/blog/archives/2005/08/new_cryptanalyt.htmlhttp://www.cwi.nl/news/2017/cwi-and-google-announce-first-collision-industry-security-standard-sha-1http://www.securityfocus.com/bid/12577