CVE-2005-4900
mediumpriority · track · 24OT risk · elevatedEPSS 0.009 · 60 %ileEURUUSEPSS · scored 2026-10-27
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
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (4)
Products and version ranges known to be affected.
also known as (5)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (34)
External citations — patches, advisories, analysis.
- http://ia.cr/2007/474cnnvd
- http://shattered.io/cnnvd
- http://www.cwi.nl/news/2017/cwi-and-google-announce-first-collision-industry-security-standard-sha-1cnnvd
- https://arstechnica.com/security/2017/02/at-deaths-door-for-years-widely-used-sha1-function-is-now-dead/cnnvd
- https://kc.mcafee.com/corporate/index?page=content&id=SB10340cnnvd
- https://security.googleblog.com/2015/12/an-update-on-sha-1-certificates-in.htmlcnnvd
- https://security.googleblog.com/2017/02/announcing-first-sha1-collision.htmlcnnvd
- https://sites.google.com/site/itstheshappeningcnnvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan