# CVE-2022-31121: Improper Input Validation in fabric hyperledger

> A malformed consensus request can crash the orderer node in Hyperledger Fabric, requiring an upgrade to restore service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jul 2022
- **Updated:** 23 Apr 2025
- **Also known as:** BIT-hyperledger-fabric-orderer-2022-31121, BIT-hyperledger-fabric-peer-2022-31121, BIT-hyperledger-fabric-tools-2022-31121, GHSA-72x4-cq6r-jp4p

## What is CVE-2022-31121?

CVE-2022-31121 is a high-severity denial of service vulnerability in hyperledger fabric, published on 7 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2022-31121?

7 open source packages ship an affected version, including github.com/hyperledger/fabric, hyperledger-fabric-orderer and hyperledger-fabric-peer. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/hyperledger/fabric` | Go | All versions | 2.2.7 |
| `github.com/hyperledger/fabric` | Go | All versions | 2.2.7 |
| `github.com/hyperledger/fabric` | Go | From 2.3.0 | 2.4.5 |
| `github.com/hyperledger/fabric` | Go | From 2.3.0 | 2.4.5 |
| `hyperledger-fabric-orderer` | Bitnami | All versions | 2.2.7, 2.4.5 |
| `hyperledger-fabric-peer` | Bitnami | All versions | 2.2.7, 2.4.5 |
| `hyperledger-fabric-tools` | Bitnami | All versions | 2.2.7, 2.4.5 |

Products: Hyperledger Fabric.

## How do I fix CVE-2022-31121?

Upgrade github.com/hyperledger/fabric to a fixed version for your release line: 2.2.7 or 2.4.5.

## Is CVE-2022-31121 being exploited?

There is no known exploitation of CVE-2022-31121 in the wild and no public exploit code.

## Other vulnerabilities in hyperledger fabric

- [CVE-2026-41586](https://insights.sbomify.com/CVE-2026-41586/): ObjectInputStream.readObject() without ObjectInputFilter in fabric-sdk-java allows Java deserialization RCE (critical 9.3)
- [CVE-2022-45196](https://insights.sbomify.com/CVE-2022-45196/): Denial of service in n/a (high 7.5)
- [CVE-2023-46132](https://insights.sbomify.com/CVE-2023-46132/): Crosslinking transaction attack in hyperledger/fabric (high 7.1)
- [CVE-2022-36023](https://insights.sbomify.com/CVE-2022-36023/): Remote denial of service in Hyperledger Fabric Gateway (high 7.0)
- [CVE-2024-45244](https://insights.sbomify.com/CVE-2024-45244/): Hyperledger Fabric does not verify request has a timestamp within the expected time window (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-31121 and fix it if it is affected.

What it is: CVE-2022-31121 is a high-severity denial of service vulnerability in hyperledger fabric, published on 7 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-31121 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/hyperledger/fabric (Go): affected all versions; fixed in 2.2.7
- github.com/hyperledger/fabric (Go): affected all versions; fixed in 2.2.7
- github.com/hyperledger/fabric (Go): affected from 2.3.0; fixed in 2.4.5
- github.com/hyperledger/fabric (Go): affected from 2.3.0; fixed in 2.4.5
- hyperledger-fabric-orderer (Bitnami): affected all versions; fixed in 2.2.7, 2.4.5
- hyperledger-fabric-peer (Bitnami): affected all versions; fixed in 2.2.7, 2.4.5
- hyperledger-fabric-tools (Bitnami): affected all versions; fixed in 2.2.7, 2.4.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-31121/ (Markdown: https://insights.sbomify.com/CVE-2022-31121/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-31121
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-31121
- OSV: https://osv.dev/vulnerability/CVE-2022-31121

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-31121/
Summaries are generated and may contain mistakes; the official description above is the record.