Libp2p js-libp2p
libp2p: gossipsub creates a permanent topics-map entry per distinct subscription with no cap in the default config
libp2p is a JavaScript implementation of the libp2p networking stack. Prior to 17.0.0, the @libp2p/gossipsub default configuration allows a connected remote peer to submit unsigned subscription RPC metadata for arbitrarily many distinct topic strings. handleReceivedSubscription in packages/gossipsub/src/gossipsub.ts creates a persistent topics-map entry for each accepted topic, while allowedTopics is unset by default, decodeRpc maxSubscriptions limits only one RPC rather than aggregate topic bytes, and peer scoring has no subscription-volume penalty. A single peer can therefore grow the topics map and committed heap toward out-of-memory conditions, and disconnecting additionally causes removePeer to scan all accumulated topic entries. This issue is fixed in version 17.0.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 3.3.9
Fixed in 3.3.9
- < 17.0.0
Fixed in 17.0.0
Mitigation
Upgrade js-libp2p to 3.3.9 or later.
Upgrade gossipsub to 17.0.0 or later.
References
- Vendor advisory github.com/libp2p/js-libp2p/security/advisorie…
- Patch github.com/libp2p/js-libp2p/pull/3593
- Patch github.com/libp2p/js-libp2p/commit/d5534174d8b…
1 more
- Release notes github.com/libp2p/js-libp2p/releases/tag/gossi…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.