GHSA-XJ59-9QJV-FR54

Vulnerability from github – Published: 2022-05-01 02:31 – Updated: 2025-04-12 13:05
VLAI?
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.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2005-4900"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-326"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2016-10-14T16:59:00Z",
    "severity": "MODERATE"
  },
  "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": "GHSA-xj59-9qjv-fr54",
  "modified": "2025-04-12T13:05:40Z",
  "published": "2022-05-01T02:31:49Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2005-4900"
    },
    {
      "type": "WEB",
      "url": "https://arstechnica.com/security/2017/02/at-deaths-door-for-years-widely-used-sha1-function-is-now-dead"
    },
    {
      "type": "WEB",
      "url": "https://kc.mcafee.com/corporate/index?page=content\u0026id=SB10340"
    },
    {
      "type": "WEB",
      "url": "https://security.googleblog.com/2015/12/an-update-on-sha-1-certificates-in.html"
    },
    {
      "type": "WEB",
      "url": "https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html"
    },
    {
      "type": "WEB",
      "url": "https://sites.google.com/site/itstheshappening"
    },
    {
      "type": "WEB",
      "url": "https://www.schneier.com/blog/archives/2005/02/sha1_broken.html"
    },
    {
      "type": "WEB",
      "url": "https://www.schneier.com/blog/archives/2005/08/new_cryptanalyt.html"
    },
    {
      "type": "WEB",
      "url": "http://ia.cr/2007/474"
    },
    {
      "type": "WEB",
      "url": "http://shattered.io"
    },
    {
      "type": "WEB",
      "url": "http://www.cwi.nl/news/2017/cwi-and-google-announce-first-collision-industry-security-standard-sha-1"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/bid/12577"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

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…

Detection rules are retrieved from Rulezet.

Loading…

Loading…