CVE-2005-4900 (GCVE-0-2005-4900)
Vulnerability from cvelistv5 – Published: 2016-10-14 16:00 – Updated: 2024-08-08 00:01
VLAI?
Summary
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.
Severity ?
No CVSS data available.
CWE
- n/a
Assigner
References
| URL | Tags | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||||||||||||||||||||
{
"containers": {
"adp": [
{
"providerMetadata": {
"dateUpdated": "2024-08-08T00:01:23.514Z",
"orgId": "af854a3a-2127-422b-91ae-364da2661108",
"shortName": "CVE"
},
"references": [
{
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "https://sites.google.com/site/itstheshappening"
},
{
"name": "12577",
"tags": [
"vdb-entry",
"x_refsource_BID",
"x_transferred"
],
"url": "http://www.securityfocus.com/bid/12577"
},
{
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "http://shattered.io/"
},
{
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "https://www.schneier.com/blog/archives/2005/08/new_cryptanalyt.html"
},
{
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "http://www.cwi.nl/news/2017/cwi-and-google-announce-first-collision-industry-security-standard-sha-1"
},
{
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "http://ia.cr/2007/474"
},
{
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html"
},
{
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "https://security.googleblog.com/2015/12/an-update-on-sha-1-certificates-in.html"
},
{
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "https://www.schneier.com/blog/archives/2005/02/sha1_broken.html"
},
{
"tags": [
"x_refsource_MISC",
"x_transferred"
],
"url": "https://arstechnica.com/security/2017/02/at-deaths-door-for-years-widely-used-sha1-function-is-now-dead/"
},
{
"tags": [
"x_refsource_CONFIRM",
"x_transferred"
],
"url": "https://kc.mcafee.com/corporate/index?page=content\u0026id=SB10340"
}
],
"title": "CVE Program Container"
}
],
"cna": {
"affected": [
{
"product": "n/a",
"vendor": "n/a",
"versions": [
{
"status": "affected",
"version": "n/a"
}
]
}
],
"datePublic": "2005-02-15T00:00:00.000Z",
"descriptions": [
{
"lang": "en",
"value": "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."
}
],
"problemTypes": [
{
"descriptions": [
{
"description": "n/a",
"lang": "en",
"type": "text"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2020-12-09T08:06:17.000Z",
"orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
"shortName": "mitre"
},
"references": [
{
"tags": [
"x_refsource_MISC"
],
"url": "https://sites.google.com/site/itstheshappening"
},
{
"name": "12577",
"tags": [
"vdb-entry",
"x_refsource_BID"
],
"url": "http://www.securityfocus.com/bid/12577"
},
{
"tags": [
"x_refsource_MISC"
],
"url": "http://shattered.io/"
},
{
"tags": [
"x_refsource_MISC"
],
"url": "https://www.schneier.com/blog/archives/2005/08/new_cryptanalyt.html"
},
{
"tags": [
"x_refsource_MISC"
],
"url": "http://www.cwi.nl/news/2017/cwi-and-google-announce-first-collision-industry-security-standard-sha-1"
},
{
"tags": [
"x_refsource_MISC"
],
"url": "http://ia.cr/2007/474"
},
{
"tags": [
"x_refsource_MISC"
],
"url": "https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html"
},
{
"tags": [
"x_refsource_MISC"
],
"url": "https://security.googleblog.com/2015/12/an-update-on-sha-1-certificates-in.html"
},
{
"tags": [
"x_refsource_MISC"
],
"url": "https://www.schneier.com/blog/archives/2005/02/sha1_broken.html"
},
{
"tags": [
"x_refsource_MISC"
],
"url": "https://arstechnica.com/security/2017/02/at-deaths-door-for-years-widely-used-sha1-function-is-now-dead/"
},
{
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://kc.mcafee.com/corporate/index?page=content\u0026id=SB10340"
}
],
"x_legacyV4Record": {
"CVE_data_meta": {
"ASSIGNER": "cve@mitre.org",
"ID": "CVE-2005-4900",
"STATE": "PUBLIC"
},
"affects": {
"vendor": {
"vendor_data": [
{
"product": {
"product_data": [
{
"product_name": "n/a",
"version": {
"version_data": [
{
"version_value": "n/a"
}
]
}
}
]
},
"vendor_name": "n/a"
}
]
}
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"lang": "eng",
"value": "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."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "eng",
"value": "n/a"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "https://sites.google.com/site/itstheshappening",
"refsource": "MISC",
"url": "https://sites.google.com/site/itstheshappening"
},
{
"name": "12577",
"refsource": "BID",
"url": "http://www.securityfocus.com/bid/12577"
},
{
"name": "http://shattered.io/",
"refsource": "MISC",
"url": "http://shattered.io/"
},
{
"name": "https://www.schneier.com/blog/archives/2005/08/new_cryptanalyt.html",
"refsource": "MISC",
"url": "https://www.schneier.com/blog/archives/2005/08/new_cryptanalyt.html"
},
{
"name": "http://www.cwi.nl/news/2017/cwi-and-google-announce-first-collision-industry-security-standard-sha-1",
"refsource": "MISC",
"url": "http://www.cwi.nl/news/2017/cwi-and-google-announce-first-collision-industry-security-standard-sha-1"
},
{
"name": "http://ia.cr/2007/474",
"refsource": "MISC",
"url": "http://ia.cr/2007/474"
},
{
"name": "https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html",
"refsource": "MISC",
"url": "https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html"
},
{
"name": "https://security.googleblog.com/2015/12/an-update-on-sha-1-certificates-in.html",
"refsource": "MISC",
"url": "https://security.googleblog.com/2015/12/an-update-on-sha-1-certificates-in.html"
},
{
"name": "https://www.schneier.com/blog/archives/2005/02/sha1_broken.html",
"refsource": "MISC",
"url": "https://www.schneier.com/blog/archives/2005/02/sha1_broken.html"
},
{
"name": "https://arstechnica.com/security/2017/02/at-deaths-door-for-years-widely-used-sha1-function-is-now-dead/",
"refsource": "MISC",
"url": "https://arstechnica.com/security/2017/02/at-deaths-door-for-years-widely-used-sha1-function-is-now-dead/"
},
{
"name": "https://kc.mcafee.com/corporate/index?page=content\u0026id=SB10340",
"refsource": "CONFIRM",
"url": "https://kc.mcafee.com/corporate/index?page=content\u0026id=SB10340"
}
]
}
}
}
},
"cveMetadata": {
"assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
"assignerShortName": "mitre",
"cveId": "CVE-2005-4900",
"datePublished": "2016-10-14T16:00:00.000Z",
"dateReserved": "2016-10-14T00:00:00.000Z",
"dateUpdated": "2024-08-08T00:01:23.514Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.1"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…