How severe is GHSA-6fcr-9h9g-23fq?

GHSA-6fcr-9h9g-23fq has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-6fcr-9h9g-23fq?

GHSA-6fcr-9h9g-23fq affects the following packages: ipfs-bitswap (npm). Ecosystems affected: npm.

How do I fix GHSA-6fcr-9h9g-23fq?

Update ipfs-bitswap to 0.24.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6fcr-9h9g-23fq is resolved across your whole dependency graph.

How do I detect GHSA-6fcr-9h9g-23fq in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ipfs-bitswap, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6fcr-9h9g-23fq if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-6fcr-9h9g-23fq actively exploited in the wild?

No public exploit code has been indexed for GHSA-6fcr-9h9g-23fq yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-6fcr-9h9g-23fq published, and has it been updated?

GHSA-6fcr-9h9g-23fq was published on September 2, 2020 and was last updated on December 7, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

MEDIUM severity

Denial of Service in ipfs-bitswapGHSA-6fcr-9h9g-23fq

MEDIUMFix: ipfs/js-ipfs-bitswap#194

GHSA-6fcr-9h9g-23fq is a medium-severity (CVSS 5.9) vulnerability in ipfs-bitswap. A fix is available for ipfs-bitswap — see the affected versions and patch details below.

Published

Sep 2, 2020

Updated

Dec 7, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 7, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

22other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

ipfs-bitswapnpm

8Kdownloads / week

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`ipfs-bitswap`	all versions	0.24.1`npm install ipfs-bitswap@0.24.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ipfs-bitswap, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ipfs-bitswap to 0.24.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6fcr-9h9g-23fq is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-6fcr-9h9g-23fq in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works