GHSA-72x4-cq6r-jp4p
HIGHHyperledger Fabric vulnerable to Improper Input Validation in orderer/common/cluster consensus request
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
github.com/hyperledger/fabric🐹github.com/hyperledger/fabricReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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:
- Open an issue in Hyperledger Fabric repository
Credits
Thank you to Haosheng Wang of OPPO ZIWU Security Lab for this disclosure.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/hyperledger/fabric | all versions | 2.2.7 |
| 🐹Go | github.com/hyperledger/fabric | ≥ 2.3.0&&< 2.4.5 | 2.4.5 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hyperledger/fabric. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/hyperledger/fabric to 2.2.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-72x4-cq6r-jp4p is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-72x4-cq6r-jp4p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-72x4-cq6r-jp4p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-72x4-cq6r-jp4p in your dependencies?
O3 detects GHSA-72x4-cq6r-jp4p across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.