Boxo bitswap/server: DOS unbounded persistent memory leak
ipfs boxo
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/ipfs/go-libipfs Go |
|
|
| github.com/ipfs/go-bitswap Go |
|
|
ipfs boxo
| Product | Affected | Fixed in |
|---|---|---|
| github.com/ipfs/go-libipfs Go |
|
|
| github.com/ipfs/go-bitswap Go |
|
|
Boxo, formerly known as go-libipfs, is a library for building IPFS applications and implementations. In versions 0.4.0 and 0.5.0, if an attacker is able allocate arbitrary many bytes in the Bitswap server, those allocations are lasting even if the connection is closed. This affects users accepting untrusted connections with the Bitswap server and also affects users using the old API stubs at `github.com/ipfs/go-libipfs/bitswap` because users then transitively import `github.com/ipfs/go-libipfs/bitswap/server`. Boxo versions 0.6.0 and 0.4.1 contain a patch for this issue. As a workaround, those who are using the stub object at `github.com/ipfs/go-libipfs/bitswap` not taking advantage of the features provided by the server can refactor their code to use the new split API that will allow them to run in a client only mode: `github.com/ipfs/go-libipfs/bitswap/client`.
From the CVE record · GitHub_M
Affected Boxo Bitswap server code retains attacker-triggered byte allocations after a connection closes. Users accepting untrusted Bitswap connections are affected; users importing the old `github.com/ipfs/go-libipfs/bitswap` API stubs are also affected because they transitively import the server.
Check IPFS applications using Go `github.com/ipfs/go-libipfs` versions >=0.5.0 <0.6.0 or <0.4.1, or `github.com/ipfs/go-bitswap` versions <0.12.0.