Denial of Service in ipfs-bitswap

published 2020-09-02 6y ago modified 2023-12-07 2y ago

cvss: 5.9; 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

Versions of `ipfs-bitswap` prior to 0.24.1 are vulnerable to Denial of Service (DoS). The package put unwanted blocks in the blockstore, which could be used to exhaust system resources in specific conditions.

## Recommendation

Upgrade to version 0.24.1 or later.

Patch / fix

fixed in 1 links 1

npm ipfs-bitswap 0.24.1

github.com/ipfs/js-ipfs-bitswap#194 pull request

Is GHSA-6fcr-9h9g-23fq 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 Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	5.9	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem	package	affected	fixed in
npm	ipfs-bitswap	<0.24.1	0.24.1

Classification

Weakness

CWE-400 Uncontrolled Resource Consumption

References

github.com /ipfs/js-ipfs-bitswap/pull/194
web
github.com /ipfs/js-ipfs-bitswap
package
snyk.io /vuln/SNYK-JS-IPFSBITSWAP-174847
web
npmjs.com /advisories/916
web

Sources

GitHub Advisory GHSA-6fcr-9h9g-23fq

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.