Vulnerability in Google Chrome
CVE-2005-4900
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.9 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
EPSS 0.009, 60.0th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (nicolaswill/VulnerablePOS). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- sites.google.com/site/itstheshappening (Third Party Advisory)
- www.securityfocus.com/bid/12577 (vdb-entry)
- shattered.io/
- www.schneier.com/blog/archives/2005/08/new_cryptanalyt.html (Third Party Advisory)
- www.cwi.nl/news/2017/cwi-and-google-announce-first-collision-industry-security-…
- ia.cr/2007/474 (Third Party Advisory)
- security.googleblog.com/2017/02/announcing-first-sha1-collision.html
- security.googleblog.com/2015/12/an-update-on-sha-1-certificates-in.html (Third Party Advisory)
- www.schneier.com/blog/archives/2005/02/sha1_broken.html (Third Party Advisory)
- arstechnica.com/security/2017/02/at-deaths-door-for-years-widely-used-sha1-func…