gsd-2005-4900
Vulnerability from gsd
Modified
2023-12-13 01:20
Details
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.
Aliases
Aliases
{
"GSD": {
"alias": "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.",
"id": "GSD-2005-4900",
"references": [
"https://www.suse.com/security/cve/CVE-2005-4900.html"
]
},
"gsd": {
"metadata": {
"exploitCode": "unknown",
"remediation": "unknown",
"reportConfidence": "confirmed",
"type": "vulnerability"
},
"osvSchema": {
"aliases": [
"CVE-2005-4900"
],
"details": "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.",
"id": "GSD-2005-4900",
"modified": "2023-12-13T01:20:09.924663Z",
"schema_version": "1.4.0"
}
},
"namespaces": {
"cve.org": {
"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"
}
]
}
},
"nvd.nist.gov": {
"configurations": {
"CVE_data_version": "4.0",
"nodes": [
{
"children": [],
"cpe_match": [
{
"cpe23Uri": "cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*",
"cpe_name": [],
"versionEndIncluding": "47.0.2526.111",
"vulnerable": true
}
],
"operator": "OR"
}
]
},
"cve": {
"CVE_data_meta": {
"ASSIGNER": "cve@mitre.org",
"ID": "CVE-2005-4900"
},
"data_format": "MITRE",
"data_type": "CVE",
"data_version": "4.0",
"description": {
"description_data": [
{
"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."
}
]
},
"problemtype": {
"problemtype_data": [
{
"description": [
{
"lang": "en",
"value": "CWE-326"
}
]
}
]
},
"references": {
"reference_data": [
{
"name": "http://ia.cr/2007/474",
"refsource": "MISC",
"tags": [
"Third Party Advisory"
],
"url": "http://ia.cr/2007/474"
},
{
"name": "https://sites.google.com/site/itstheshappening",
"refsource": "MISC",
"tags": [
"Third Party Advisory"
],
"url": "https://sites.google.com/site/itstheshappening"
},
{
"name": "https://www.schneier.com/blog/archives/2005/08/new_cryptanalyt.html",
"refsource": "MISC",
"tags": [
"Third Party Advisory"
],
"url": "https://www.schneier.com/blog/archives/2005/08/new_cryptanalyt.html"
},
{
"name": "https://www.schneier.com/blog/archives/2005/02/sha1_broken.html",
"refsource": "MISC",
"tags": [
"Third Party Advisory"
],
"url": "https://www.schneier.com/blog/archives/2005/02/sha1_broken.html"
},
{
"name": "https://security.googleblog.com/2015/12/an-update-on-sha-1-certificates-in.html",
"refsource": "MISC",
"tags": [
"Third Party Advisory"
],
"url": "https://security.googleblog.com/2015/12/an-update-on-sha-1-certificates-in.html"
},
{
"name": "https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html",
"refsource": "MISC",
"tags": [],
"url": "https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html"
},
{
"name": "https://arstechnica.com/security/2017/02/at-deaths-door-for-years-widely-used-sha1-function-is-now-dead/",
"refsource": "MISC",
"tags": [],
"url": "https://arstechnica.com/security/2017/02/at-deaths-door-for-years-widely-used-sha1-function-is-now-dead/"
},
{
"name": "http://www.cwi.nl/news/2017/cwi-and-google-announce-first-collision-industry-security-standard-sha-1",
"refsource": "MISC",
"tags": [],
"url": "http://www.cwi.nl/news/2017/cwi-and-google-announce-first-collision-industry-security-standard-sha-1"
},
{
"name": "http://shattered.io/",
"refsource": "MISC",
"tags": [],
"url": "http://shattered.io/"
},
{
"name": "12577",
"refsource": "BID",
"tags": [],
"url": "http://www.securityfocus.com/bid/12577"
},
{
"name": "https://kc.mcafee.com/corporate/index?page=content\u0026id=SB10340",
"refsource": "CONFIRM",
"tags": [],
"url": "https://kc.mcafee.com/corporate/index?page=content\u0026id=SB10340"
}
]
}
},
"impact": {
"baseMetricV2": {
"cvssV2": {
"accessComplexity": "MEDIUM",
"accessVector": "NETWORK",
"authentication": "NONE",
"availabilityImpact": "NONE",
"baseScore": 4.3,
"confidentialityImpact": "PARTIAL",
"integrityImpact": "NONE",
"vectorString": "AV:N/AC:M/Au:N/C:P/I:N/A:N",
"version": "2.0"
},
"exploitabilityScore": 8.6,
"impactScore": 2.9,
"obtainAllPrivilege": false,
"obtainOtherPrivilege": false,
"obtainUserPrivilege": false,
"severity": "MEDIUM",
"userInteractionRequired": false
},
"baseMetricV3": {
"cvssV3": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.9,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "HIGH",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
"version": "3.0"
},
"exploitabilityScore": 2.2,
"impactScore": 3.6
}
},
"lastModifiedDate": "2020-12-09T09:15Z",
"publishedDate": "2016-10-14T16:59Z"
}
}
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…