CVE-2018-3756

Hyperledger Iroha versions v1.0beta and v1.0.0beta-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...

PYSEC-2018-150

Hyperledger Iroha versions v1.0beta and v1.0.0beta-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...

Design/Logic Flaw

Hyperledger Iroha versions v1.0beta and v1.0.0beta-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...

CVE-2018-3756

Hyperledger Iroha versions v1.0_beta and v1.0.0_beta-1 are vulnerable to a transaction and block signature verification bypass in the transaction and block validator. This flaw allows a single node to sign a transaction and/or block multiple times, each with a random nonce, and have other validat...

CVE-2018-3756

Hyperledger Iroha versions v1.0beta and v1.0.0beta-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...

CVE-2018-3756

Hyperledger Iroha versions v1.0beta and v1.0.0beta-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...

PT-2018-19205

Name of the Vulnerable Software and Affected Versions Hyperledger Iroha versions v1.0 beta through v1.0.0 beta-1 Description The issue allows a single node to bypass transaction and block signature verification in the transaction and block validator. This can be achieved by signing a transaction...

CVE-2018-3756: Improper Verification of Cryptographic Signature

Hyperledger Iroha versions v1.0beta and v1.0.0beta-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...

PT-2018-16177

Name of the Vulnerable Software and Affected Versions Hyperledger Iroha versions v1.0 beta through v1.0.0 beta-1 Description The issue allows a single node to bypass transaction and block signature verification in the transaction and block validator. This can be achieved by signing a transaction...

Hyperledger: many commands can be manipulated to delete identities or affiliations

Introduction: The Faric-ca data in http body and authorization header for many commands that send from client to server are protected by signature. But I find the identity and affiliation commands still have the risk to be manipulated. Hacker can manipulate most other commands to delete identitie...

Blockchain technology: not just for cryptocurrency

Imagine a place where you can safely store all your personal information and only you decide who has access to it. You can choose which parts of that information you want to share, and you can just as easily revoke that access. If this place ever comes into existence, I am willing to bet it will ...

Replay Attack

github.com/hyperledger/fabric is vulnerable to replay attacks. The library does not verify that the TxID of a transaction is unique, allowing a malicious user to possibly overwrite a currently existing transactionID...

Denial Of Service (DoS) Via Memory Consumption

github.com/hyperledger/fabric is vulnerable to denial of service DoS attacks. The attacks exists because it uses hash field in the protos comparator function to compare two large blocks disseminated. However, it does not prevent sending of arbitrary hash via the hash field of the DataMsg, leading...