GHSA-9w7j-q3xw-p9vh json
Hyperledger Fabric subject to Denial of Service via non-validated request
published 4y ago modified 3y ago also CVE-2022-35253
- cvss
- 7.5
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
A vulnerability exists in Hyperledger Fabric < 2.4 could allow an attacker to construct a non-validated request that could cause a denial of service attack. The peer gateway service tries to extract channel and chaincode information from the signed proposal, but it doesn't check the proposal fields for validity. Therefore a malformed proposal might end up crashing the peer service. This issue has been patched in 2.4.6. There are no known workarounds.
Patch / fix
- go github.com/hyperledger/fabric 2.4.6
- github.com/hyperledger/fabric#3572 pull request
- github.com/hyperledger/fabric#3576 pull request
- github.com/hyperledger/fabric#3577 pull request
Is GHSA-9w7j-q3xw-p9vh in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/hyperledger/fabric | <2.4.6 |
2.4.6 |
Classification
References
Sources
- GitHub Advisory GHSA-9w7j-q3xw-p9vh
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.