Sliver does not restricted traffic between Wireguard clients.
BishopFox sliver
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/BishopFox/sliver Go |
|
|
| github.com/bishopfox/sliver Go |
|
|
BishopFox sliver
| Product | Affected | Fixed in |
|---|---|---|
| github.com/BishopFox/sliver Go |
|
|
| github.com/bishopfox/sliver Go |
|
|
Sliver is a command and control framework that uses a custom Wireguard netstack. In versions 1.5.43 and earlier, and in development version 1.6.0-dev, the netstack does not limit traffic between Wireguard clients. This allows clients to communicate with each other unrestrictedly, potentially enabling leaked or recovered keypairs to be used to attack operators or allowing port forwardings to be accessible from other implants.
From the CVE record · GitHub_M
Sliver’s custom Wireguard netstack does not limit traffic between clients in versions 1.5.43 and earlier or in 1.6.0-dev. A client with a leaked or recovered keypair could use that access to attack operators, and port forwardings may be accessible from other implants. No user interaction is described.
Engineers running BishopFox Sliver or either Go package, github.com/BishopFox/sliver or github.com/bishopfox/sliver, should check versions earlier than 1.5.44 and the 1.6.0-dev development version.