pysec-2018-150
Vulnerability from pysec
Published
2018-06-01 19:29
Modified
2024-11-21 14:22
Details

Hyperledger Iroha versions v1.0_beta and v1.0.0_beta-1 are vulnerable to transaction and block signature verification bypass in the transaction and block validator allowing a single node to sign a transaction and/or block multiple times, each with a random nonce, and have other validating nodes accept them as separate valid signatures.

Aliases



{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "iroha",
        "purl": "pkg:pypi/iroha"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.0.1",
        "0.0.2",
        "0.0.5.1",
        "0.0.5.2",
        "0.0.5.3",
        "0.0.5.4",
        "0.0.5.5",
        "0.0.5.dev1",
        "1.0.0",
        "1.4.1",
        "1.4.1.1",
        "1.6.0.1",
        "1.6.0.2"
      ]
    }
  ],
  "aliases": [
    "CVE-2018-3756"
  ],
  "details": "Hyperledger Iroha versions v1.0_beta and v1.0.0_beta-1 are vulnerable to transaction and block signature verification bypass in the transaction and block validator allowing a single node to sign a transaction and/or block multiple times, each with a random nonce, and have other validating nodes accept them as separate valid signatures.",
  "id": "PYSEC-2018-150",
  "modified": "2024-11-21T14:22:52.162008Z",
  "published": "2018-06-01T19:29:00Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/hyperledger/iroha/releases/tag/v1.0.0_beta-2"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "withdrawn": "2024-11-22T04:37:04Z"
}


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 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.