Homepage

@libp2p/gossipsub@15.0.9-d447a9944

A typescript implementation of gossipsub

  • latest version

    16.1.1

  • latest non vulnerable version

    16.1.1

  • first published

    10 months ago

  • latest version published

    12 days ago

  • licenses detected

  • View gossipsub package health on Snyk  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the @libp2p/gossipsub package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • H
    Allocation of Resources Without Limits or Throttling

    @libp2p/gossipsub is an A typescript implementation of gossipsub

    Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the defaultDecodeRpcLimits in which maxIhaveMessageIDs and maxIwantMessageIDs are set to Infinity, allowing oversized IHAVE and IWANT control message arrays to be processed in message/decodeRpc.ts and gossipsub.ts. An attacker can exhaust CPU resources and block the Node.js event loop by sending large arrays of message IDs.

    How to fix Allocation of Resources Without Limits or Throttling?

    Upgrade @libp2p/gossipsub to version 15.0.23-d888f182f or higher.

    <15.0.23-d888f182f
    • H
    Missing Release of Memory after Effective Lifetime

    @libp2p/gossipsub is an A typescript implementation of gossipsub

    Affected versions of this package are vulnerable to Missing Release of Memory after Effective Lifetime through unbounded growth of the topics data structure when processing subscription requests. An attacker can exhaust system memory and cause a process crash by sending a large number of unique topic subscriptions in a single RPC frame, leading to significant heap consumption and eventual out-of-memory termination. Memory is not reclaimed even after the attacker disconnects, as empty Sets persist in the topics map for the lifetime of the process.

    How to fix Missing Release of Memory after Effective Lifetime?

    Upgrade @libp2p/gossipsub to version 15.0.23 or higher.

    <15.0.23
    Go back to all versions of this package