CVE-2022-31121

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

Specific Go Packages Affected

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

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.

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.

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2022-31121 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.2.7, 2.4.5); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Fixed in v2.2.7 and v2.4.5.

1. What is CVE-2022-31121? CVE-2022-31121 is a high-severity improper input validation vulnerability in github.com/hyperledger/fabric (go), affecting versions < 2.2.7. It is fixed in 2.2.7, 2.4.5. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2022-31121? CVE-2022-31121 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/hyperledger/fabric are affected by CVE-2022-31121? github.com/hyperledger/fabric (go) versions < 2.2.7 is affected.
4. Is there a fix for CVE-2022-31121? Yes. CVE-2022-31121 is fixed in 2.2.7, 2.4.5. Upgrade to this version or later.
5. Is CVE-2022-31121 exploitable, and should I be worried? Whether CVE-2022-31121 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-31121 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-31121?
   • Upgrade github.com/hyperledger/fabric to 2.2.7 or later
   • Upgrade github.com/hyperledger/fabric to 2.4.5 or later

Other vulnerabilities in github.com/hyperledger/fabric