Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Go package

github.com/ipfs/go-libipfs

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.2GoPublished

    Boxo bitswap/server: DOS unbounded persistent memory leak

    CVE-2023-25568 · GHSA-m974-xj4j-7qv5

    Affected
    • Go github.com/ipfs/go-libipfs >= 0.5.0, < 0.6.0; < 0.4.1
    Fixed in
    0.6.00.4.1· Vendor fix available
    Issue
    Impact An attacker is able allocate arbitrarily many bytes in the Bitswap server by sending many WANTBLOCK and or WANTHAVE requests which are queued in an unbounded queue, with allocations that persist even if the connection is closed. This affects users accepting untrusted connections with the Bitswap server, this also affects users using the old API stubs at github.com/ipfs/boxo/bitswap because it transitively uses github.com/ipfs/boxo/bitswap/server. We have renamed go-libipfs to boxo; this document uses both terms interchangeably. The version numbers for both are applicable, as they share the same historical timeline. Remediation Apply one of: - Update boxo to v0.6.0 or later - Update boxo to v0.4.1 Note that v0.5.0 is NOT safe, v0.4.1 is a backport of the v0.6.0 security fixes on top of v0.4.0. Mitigations 1. The server now limits how many wantlist entries per peer it knows. The MaxQueuedWantlistEntriesPerPeer option allows configuring how many wantlist entries the server…

    Recommended action: Upgrade to 0.6.0 or 0.4.1 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →