Skip to content

Hyperledger Fabric vulnerable to Improper Input Validation in orderer/common/cluster consensus request

High severity GitHub Reviewed Published Jul 7, 2022 in hyperledger/fabric • Updated Oct 2, 2023

Package

gomod github.com/hyperledger/fabric (Go)

Affected versions

< 2.2.7
>= 2.3.0, < 2.4.5

Patched versions

2.2.7
2.4.5

Description

Impact

If a consensus client sends a malformed consensus request to an orderer it may crash the orderer node.
This fix checks for the malformed consensus request and returns an error to the consensus client.

Specific Go Packages Affected

github.com/hyperledger/fabric/orderer/common/cluster

Patches

Fixed in v2.2.7 and v2.4.5.

Workarounds

None, users must upgrade to v2.2.7 or v2.4.5.

References

https://github.com/hyperledger/fabric/releases/tag/v2.2.7
https://github.com/hyperledger/fabric/releases/tag/v2.4.5

For more information

If you have any questions or comments about this advisory:

Credits

Thank you to Haosheng Wang of OPPO ZIWU Security Lab for this disclosure.

References

@ryjones ryjones published to hyperledger/fabric Jul 7, 2022
Published by the National Vulnerability Database Jul 7, 2022
Published to the GitHub Advisory Database Jul 8, 2022
Reviewed Jul 8, 2022
Last updated Oct 2, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.206%
(59th percentile)

Weaknesses

CVE ID

CVE-2022-31121

GHSA ID

GHSA-72x4-cq6r-jp4p

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.