Vulnerabilities (CVE)

Filtered by vendor Hyperledger
Filtered by product Fabric
Angry Yack Logo
Total 5 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2024-45244 1 Hyperledger 1 Fabric 2025-10-06 N/A 5.3 MEDIUM
Hyperledger Fabric through 3.0.0 and 2.5.x through 2.5.9 do not verify that a request has a timestamp within the expected time window.
CVE-2022-45196 1 Hyperledger 1 Fabric 2025-05-01 N/A 7.5 HIGH
Hyperledger Fabric 2.3 allows attackers to cause a denial of service (orderer crash) by repeatedly sending a crafted channel tx with the same Channel name. NOTE: the official Fabric with Raft prevents exploitation via a locking mechanism and a check for names that already exist.
CVE-2023-46132 1 Hyperledger 1 Fabric 2024-11-21 N/A 7.1 HIGH
Hyperledger Fabric is an open source permissioned distributed ledger framework. Combining two molecules to one another, called "cross-linking" results in a molecule with a chemical formula that is composed of all atoms of the original two molecules. In Fabric, one can take a block of transactions and cross-link the transactions in a way that alters the way the peers parse the transactions. If a first peer receives a block B and a second peer receives a block identical to B but with the transacti ...

Show More

CVE-2022-36023 1 Hyperledger 1 Fabric 2024-11-21 N/A 7.0 HIGH
Hyperledger Fabric is an enterprise-grade permissioned distributed ledger framework for developing solutions and applications. If a gateway client application sends a malformed request to a gateway peer it may crash the peer node. Version 2.4.6 checks for the malformed gateway request and returns an error to the gateway client. There are no known workarounds, users must upgrade to version 2.4.6.
CVE-2022-31121 1 Hyperledger 1 Fabric 2024-11-21 5.0 MEDIUM 7.5 HIGH
Hyperledger Fabric is a permissioned distributed ledger framework. In affected versions if a consensus client sends a malformed consensus request to an orderer it may crash the orderer node. A fix has been added in commit 0f1835949 which checks for missing consensus messages and returns an error to the consensus client should the message be missing. Users are advised to upgrade to versions 2.2.7 or v2.4.5. There are no known workarounds for this issue.